From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8362 invoked by alias); 10 Nov 2005 01:27:45 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 8354 invoked by uid 22791); 10 Nov 2005 01:27:44 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 10 Nov 2005 01:27:44 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Ea1E3-0002yR-NI; Wed, 09 Nov 2005 20:27:39 -0500 Date: Thu, 10 Nov 2005 03:30:00 -0000 From: Daniel Jacobowitz To: Andreas Schwab Cc: Andrew STUBBS , gdb-patches@sources.redhat.com Subject: Re: [SH][PATCH] Disable ABI frame sniffer Message-ID: <20051110012739.GA11334@nevyn.them.org> Mail-Followup-To: Andreas Schwab , Andrew STUBBS , gdb-patches@sources.redhat.com References: <43722DEF.8060300@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-11/txt/msg00122.txt.bz2 On Wed, Nov 09, 2005 at 09:43:03PM +0100, Andreas Schwab wrote: > Andrew STUBBS 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