Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: gdb-6.5 produces infinite backtrace on ARM
Date: Wed, 06 Sep 2006 15:52:00 -0000	[thread overview]
Message-ID: <20060906155248.GA4902@nevyn.them.org> (raw)
In-Reply-To: <44FEEB57.6010807@imc-berlin.de>

On Wed, Sep 06, 2006 at 05:37:59PM +0200, Zarges, Olav wrote:
> 
> Daniel Jacobowitz wrote:
> > 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!
> > 
> 
> The stack-list-frames command does not return any stack info at all if
> error(...) is called. Therefore CDT is not discarding anything. The is
> just the error message.

Sorry - I misread your trace.  OK, I see what's generally wrong...

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-09-06 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15  8:15 Zarges, Olav
2006-08-15 12:41 ` Daniel Jacobowitz
2006-08-15 13:54   ` Zarges, Olav
2006-08-19  5:24   ` Daniel Jacobowitz
2006-08-21 11:35     ` Zarges, Olav
2006-08-21 12:42       ` Daniel Jacobowitz
2006-08-21 14:37         ` Zarges, Olav
2006-08-21 14:54           ` Daniel Jacobowitz
2006-09-06 13:32         ` Zarges, Olav
2006-09-06 14:44           ` Daniel Jacobowitz
2006-09-06 15:03             ` Zarges, Olav
2006-09-06 15:19               ` Daniel Jacobowitz
2006-09-06 15:38                 ` Zarges, Olav
2006-09-06 15:52                   ` Daniel Jacobowitz [this message]
2006-09-07 16:15                     ` Zarges, Olav
2006-09-07 17:38                       ` Daniel Jacobowitz
2006-09-10 14:49                 ` Daniel Jacobowitz
2006-09-19  1:40     ` Michael Snyder
2006-09-19  3:17       ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060906155248.GA4902@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox