This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: stack corruption?


On Jun 14, 2005, at 2:31 PM, Louis LeBlanc wrote:

#9  0x0002e9f4 in handle_check (thread=0x759b70) at myprog.c:904
#10 0x000e3134 in spawn (arg=0x759b70) at mythread.c:195
#11 0xff354978 in _lwp_start () from /usr/lib/lwp/libthread.so.1
#12 0xff354978 in _lwp_start () from /usr/lib/lwp/libthread.so.1
Previous frame identical to this frame (corrupt stack?)
(gdb)

I have changed identifying names to protect the guilty, but this is
pretty much typical.


In this particular example, the problem is that gdb didn't correctly recognize when to stop the backtrace. While lame, were you expecting something to be after _lwp_start in your stack backtrace?


Jason

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]