[omniORB] orb->destroy SIGSEGV

Duncan Grisby duncan at grisby.org
Fri Dec 5 17:38:43 GMT 2003


On Friday 5 December, jorgefm at cirsa.com wrote:

> I'm developing under SuSE Linux 8.1 (i386) - Kernel 2.4.19-4GB with omniORB
> 4.0.1.
> 
> When i call the destroy method from orb i get a segmentation fault with the
> next backtrace.

[...]
> #0  0x4031e00a in chunk_alloc () from /lib/libc.so.6
> #1  0x4031de42 in malloc ( ) from /lib/libc.so.6
> #2  0x4025c94e in operator new(unsigned) () from /usr/lib/libstdc++.so.5
> #3  0x4025caaf in operator new[ ](unsigned) () from /usr/lib/libstdc++.so.5
> #4  0x400adcfd in CORBA::string_alloc(unsigned long) ()

Segfaults in malloc are almost always due to earlier memory
corruption. Are you able to run your code under valgrind to see if
that traps it?

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --



More information about the omniORB-list mailing list