From: Aleksandar Ristovski <aristovski@qnx.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Guillaume MENANT <guillaume.menant@geensys.com>, gdb@sourceware.org
Subject: Re: Previous frame identical to this frame (corrupt stack?)
Date: Wed, 05 Mar 2008 18:08:00 -0000 [thread overview]
Message-ID: <47CED7B1.2050205@qnx.com> (raw)
In-Reply-To: <20080305171516.GA3894@adacore.com>
Joel Brobecker wrote:
>> 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 might also be experiencing a library mismatch.
>
> 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.
>
next prev parent reply other threads:[~2008-03-05 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:40 Guillaume MENANT
2008-03-05 17:26 ` Joel Brobecker
2008-03-05 18:08 ` Aleksandar Ristovski [this message]
2008-03-05 19:52 ` Andrew STUBBS
2008-03-06 2:05 ` Michael Snyder
2008-03-06 7:06 ` Guillaume MENANT
2008-03-06 10:05 ` Mark Kettenis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47CED7B1.2050205@qnx.com \
--to=aristovski@qnx.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=guillaume.menant@geensys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox