From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1858 invoked by alias); 6 Sep 2006 14:44:06 -0000 Received: (qmail 1850 invoked by uid 22791); 6 Sep 2006 14:44:05 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Wed, 06 Sep 2006 14:44:02 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GKydA-0000nr-Pm; Wed, 06 Sep 2006 10:43:56 -0400 Date: Wed, 06 Sep 2006 14:44:00 -0000 From: Daniel Jacobowitz To: "Zarges, Olav" Cc: "gdb@sourceware.org" Subject: Re: gdb-6.5 produces infinite backtrace on ARM Message-ID: <20060906144356.GA2786@nevyn.them.org> Mail-Followup-To: "Zarges, Olav" , "gdb@sourceware.org" References: <44E181DE.7040905@imc-berlin.de> <20060815124053.GA18496@nevyn.them.org> <20060819052434.GA15612@nevyn.them.org> <44E999B4.5030905@imc-berlin.de> <20060821124241.GA16416@nevyn.them.org> <44FECDF7.2050900@imc-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44FECDF7.2050900@imc-berlin.de> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00032.txt.bz2 On Wed, Sep 06, 2006 at 03:32:39PM +0200, Zarges, Olav wrote: > Daniel Jacobowitz wrote: > >> > >> is returned at the end of the backtrace? Eclipse just throws away the > >> complete backtrace for the corresponding thread. > > > > What other versions of GDB are you looking at? With older versions, it was an > > ^error; with newer it's a ~"console output message". I would not > > expect Eclipse to throw away the backtrace if there's a console output > > message. > > verifying again which component is responsible for "eating the backtrace" > I found that those messages are created by method error(_("message....")) > e.g. called from gdb/frame.c. > > error() finally throws an exception being caught by catch_exception(...) > in function mi_execute_command(...) in gdb/mi/mi-main.c. Therefore no backtrace > info is deliverd to eclipse via GDB/MI. > > I'm using GDB 6.5 and it looks to me that it still creates an ^error. What > exactly means 'with older versions'? How can I upgrade. The error should be caught in backtrace_command now. The finished output should still be printed. -- Daniel Jacobowitz CodeSourcery