From: "David S. Miller" <davem@davemloft.net>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add sparc64-linux sigtramp support
Date: Thu, 21 Apr 2005 21:55:00 -0000 [thread overview]
Message-ID: <20050421144901.6fa89749.davem@davemloft.net> (raw)
In-Reply-To: <200504212120.j3LLKB42010991@elgar.sibelius.xs4all.nl>
On Thu, 21 Apr 2005 23:20:11 +0200 (CEST)
Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> The attached patch was what I was thinking about. If it has issues
> with signal handlers, take a look at
> i386-linux-tdep.c:i386_linux_dwarf_signale_p(), That might help in the
> case DWARF2 CFI for the signal trampoline is provided.
Missing dwarf2-frame.h include in sparc64-linux-tdep.c but otherwise
it did build.
It has one of the problems I ran into last night, namely that gcc
never emits data for register %g0 (which is always zero of course).
So the dwarf2 CFI unwinder spits out:
====
During symbol reading, incomplete CFI data; unspecified registers (e.g. g0)
at 0x100778
====
But besides that I can happily report that it seems to work well
even with signal handler backtraces. I'm doing this testing against
a tree with my tramp_frame Linux changes.
The temporary workaround I did last night was to make the sparc dwarf2
CIF unwinder init_reg() routine just mark G0 as UNDEFINED. I don't
know if that's what we'd like to do long term, or if GCC should output
something for this register.
next prev parent reply other threads:[~2005-04-21 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 3:51 David S. Miller
2005-04-21 19:23 ` Mark Kettenis
2005-04-21 19:29 ` David S. Miller
2005-04-21 21:20 ` Mark Kettenis
2005-04-21 21:41 ` David S. Miller
2005-04-21 21:57 ` Mark Kettenis
2005-04-21 22:04 ` David S. Miller
2005-04-21 21:55 ` David S. Miller [this message]
2005-04-21 22:09 ` Mark Kettenis
2005-04-22 22:45 ` David S. Miller
2005-04-23 12:33 ` Mark Kettenis
2005-04-23 17:47 ` David S. Miller
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=20050421144901.6fa89749.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.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