[omniORB] Unexpected Seg Fault

[Attila Pletyak]

I've never used Purify, and I am quite sure the whole problem can be
caused by recent changes in the app. BTW, up to this time I've only used
memprof. Is this Purify is the Rational Purify? Or something else?

Can Purify help me in a situation where the segv occurs only some days
later?

TIA,

Attila Pletyak

2001-12-04, K keltez=E9ssel Duncan Grisby ezt =EDrta:
> On Monday 3 December, Attila Pletyak wrote:
>=20
> > 	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.
>=20
> [...]
> > #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
>=20
> 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?
>=20
> Cheers,
>=20
> Duncan.
>=20
> --=20
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --
>=20