This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [SH][PATCH] Disable ABI frame sniffer
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Andrew STUBBS <andrew dot stubbs at st dot com>, gdb-patches at sources dot redhat dot com
- Date: Wed, 9 Nov 2005 20:27:39 -0500
- Subject: Re: [SH][PATCH] Disable ABI frame sniffer
- References: <43722DEF.8060300@st.com> <jezmodr1rc.fsf@sykes.suse.de>
On Wed, Nov 09, 2005 at 09:43:03PM +0100, Andreas Schwab wrote:
> Andrew STUBBS <andrew.stubbs@st.com> writes:
>
> > This message is worrying if you do not know what it means, but it is
> > normally easily ignored. Unfortunately, the problem is more serious when
> > used in conjunction with 'thread apply' as the first error kills the
> > output from the rest of the threads.
>
> Does it? That's not what I get. I always see "Previous frame inner to
> this frame" in the backtrace, but that does not stop thread apply to
> continue with the next thread.
It used to. I bet Andrew is submitting patches off of a GDB 6.3 or
earlier port. In HEAD, errors during backtrace are non-fatal.
--
Daniel Jacobowitz
CodeSourcery, LLC