This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Previous frame identical to this frame (corrupt stack?)
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Guillaume MENANT <guillaume dot menant at geensys dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 5 Mar 2008 09:15:16 -0800
- Subject: Re: Previous frame identical to this frame (corrupt stack?)
- References: <15854428.post@talk.nabble.com>
> What does it means ? What have I to look at in order to check if I have an
> mistake in my program ?
You really didn't provide much information (either GDB version,
platform, etc). But it could be either:
- a corrupt call-stack, or maybe corrupt debugging info (frame info)
- a bug in GDB
You can try using GDB from CVS head to see if you have better results.
Otherwise, you will need to inspect the frame where the backtrace stops,
and verify that it is not screwed. You might also have to check the
frame info data if your executable has them.
--
Joel