This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb-6.5 produces infinite backtrace on ARM
- From: Daniel Jacobowitz <drow at false dot org>
- To: "Zarges, Olav" <Olav dot Zarges at imc-berlin dot de>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 6 Sep 2006 10:43:56 -0400
- Subject: Re: gdb-6.5 produces infinite backtrace on ARM
- 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>
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