From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix SPARC backtraces
Date: Fri, 05 Mar 2004 05:11:00 -0000 [thread overview]
Message-ID: <40480BFC.10801@gnu.org> (raw)
Message-ID: <20040305051100.U_fjz1tF6RzNIYNxjESnh3qICG_OZPIir6ZYk-hVSos@z> (raw)
In-Reply-To: <200403041010.i24AAqc2003176@elgar.kettenis.dyndns.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.
Andrew
next prev parent reply other threads:[~2004-03-05 5:11 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 ` Mark Kettenis
2004-03-19 0:09 ` Andrew Cagney [this message]
2004-03-05 5:11 ` Andrew Cagney
2004-03-19 0:09 ` Mark Kettenis
2004-03-05 15:32 ` 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=40480BFC.10801@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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