Re: gdb-6.5 produces infinite backtrace on ARM

[Daniel Jacobowitz <drow@false.org>]

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