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 11:19:15 -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> <20060906144356.GA2786@nevyn.them.org> <44FEE32E.60401@imc-berlin.de>
On Wed, Sep 06, 2006 at 05:03:10PM +0200, Zarges, Olav wrote:
>
> Daniel Jacobowitz wrote:
> > The error should be caught in backtrace_command now. The finished
> > output should still be printed.
>
> Eclipse seems to read the stack via gdb/mi commands stack-info-depth
> and stack-list-frames and that was what I was referring to (sorry).
> Please see log below. I tried to print the message with warning(...)
> and return NULL instead of calling error(...) which seems to work but
> I don't know about the side-effects this might involve.
Oh, I see. Interesting. We'll see what we can do about this; that
does make more sense.
However, since it has obviously listed a bunch of frames, CDT should
not be discarding the ones that did succeed!
--
Daniel Jacobowitz
CodeSourcery