Ronald, good day.
Wed, Apr 25, 2007 at 04:43:53PM +0200, Ronald Starink wrote:
> It's getting a bit boring, but it crashed again:
As you're messing with gdb and there is a SEGV somewhere, you can
try to use the ElectricFence memory debugger. I used it for the
C/C++ programs: it can point you to the _right_ memory overrun
location. Because you can not tell for sure if the readdir64_r is
the right place -- things can go bad earlier and the readdir64_r
issued are just the mirror of the earlier problems.
So, install ElectricFence RPM, run your program with the
LD_PRELOAD=libefence.so.0.0 and try to reproduce the bug. If you're
spawning the program under gdb from the beginning, export LD_PRELOAD
at the gdb's invocation.
EFence helped me many times, so give it a try. But I am not sure
of its interaction with the complex C++ libraries like BOOST (seems
like it is used in VDT), so no warranties here, sorry.
Shutting up for today.
Eygene Ryabinkin, RRC KI