From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix SPARC backtraces
Date: Fri, 05 Mar 2004 15:32:00 -0000 [thread overview]
Message-ID: <200403051532.i25FWcPC035548@elgar.kettenis.dyndns.org> (raw)
Message-ID: <20040305153200.C0QLpcXBGW1AAOhaoJx2Mc_f74VZ0p_h9PfzBwGbfM0@z> (raw)
In-Reply-To: <40480BFC.10801@gnu.org> (message from Andrew Cagney on Fri, 05 Mar 2004 00:11:24 -0500)
Date: Fri, 05 Mar 2004 00:11:24 -0500
From: Andrew Cagney <cagney@gnu.org>
> As discussed before on the list, this makes sure we do the full frame
> analysis even if %fp is zero. This makes us do proper backtraces if a
> frameless function was called from the outermost frame.
Should this go on the branch? It appears to make things more robust.
Shouldn't hurt, although from a user perspective it probably doesn't
matter that much, since the failure scenario only kicks in if you're
debugging "beyond main".
Anyway, committed the the branch now too.
Mark
next prev parent reply other threads:[~2004-03-05 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 10:10 Mark Kettenis
2004-03-19 0:09 ` Andrew Cagney
2004-03-05 5:11 ` Andrew Cagney
2004-03-19 0:09 ` Mark Kettenis [this message]
2004-03-05 15:32 ` Mark Kettenis
2004-03-19 0:09 ` Mark Kettenis
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=200403051532.i25FWcPC035548@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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