[omniORB] Unexpected Seg Fault
Duncan Grisby
dgrisby@uk.research.att.com
Tue, 04 Dec 2001 09:53:22 +0000
On Monday 3 December, Attila Pletyak wrote:
> I am in the process of debugging a system. It ran for 2.5 days
> continously but then it did a segmentation fault. I looked at the core
> file, but found no mention of my program, only omniORB3 libs.
[...]
> #0 0x40912032 in recv () from /lib/libc.so.6
> #1 0x4095c7ac in recv () from /lib/libpthread.so.0
> #2 0x400bbe82 in tcpSocketStrand::ll_recv () from
> /usr/lib/libomniORB3.so.0
I think it's unlikely that an omniORB bug would cause a segfault in
recv, although it's not impossible. It's most likely a memory
corruption bug in your application. Without debugging information in
the ORB, it's difficult to look further. Are you able to run your
application with Purify or something similar?
Cheers,
Duncan.
--
-- Duncan Grisby \ Research Engineer --
-- AT&T Laboratories Cambridge --
-- http://www.uk.research.att.com/~dpg1 --