From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@chello.nl>
Cc: drow@false.org, gdb-patches@sources.redhat.com, roland@redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Tue, 11 May 2004 14:49:00 -0000 [thread overview]
Message-ID: <40A0E813.2050803@gnu.org> (raw)
In-Reply-To: <200405102140.i4ALe13A001092@elgar.kettenis.dyndns.org>
> In the meantime, here's the patch from my Debian backport which should
> fix this. Pending a way to indicate 'abnormal frame' status in the
> CFI, we don't want to use it; frame_unwind_address_in_block will hit.
> 2004-01-25 Daniel Jacobowitz <drow@mvista.com>
Even with the above frame display change, this is needed. The frame
needs to identify it's type as SIGTRAMP_FRAME.
Mark?
Hmm. The DWARF CFI in the vsyscall DSO is deliberately generated such
that frame_unwind_in_block does the right thing (there is a nop in
front of __kernel_sigreturn, which is included in the FDE range, such
that us substracting one from the PC will still give us the right
Dwarf CFI).
To what extent do we need to know about SIGTRAMP_FRAME for other
purposes? I guess we need it to get stepping into/through signal
trampolines working properly, but I'd like to be certain about it.
At least that and (see above) frame_unwind_address_in_block.
Andrew
next prev parent reply other threads:[~2004-05-11 14:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 1:19 Andrew Cagney
2004-05-07 0:48 ` Roland McGrath
2004-05-07 1:31 ` Daniel Jacobowitz
2004-05-10 21:39 ` Andrew Cagney
2004-05-07 1:19 ` Andrew Cagney
2004-05-07 1:25 ` Daniel Jacobowitz
2004-05-10 21:27 ` Andrew Cagney
2004-05-11 5:15 ` Mark Kettenis
2004-05-11 14:49 ` Andrew Cagney [this message]
2004-05-11 14:53 ` Daniel Jacobowitz
[not found] ` <40A0FFB1.8030407@gnu.org>
2004-05-11 17:26 ` Daniel Jacobowitz
2004-05-12 0:28 ` Andrew Cagney
2004-05-15 20:58 ` Mark Kettenis
2004-05-17 17:14 ` Revamp sniffer; Was: " Andrew Cagney
2004-05-25 22:55 ` Andrew Cagney
2004-06-11 17:32 ` Andrew Cagney
2004-06-15 20:17 ` Andrew Cagney
2004-06-16 23:07 ` Roland McGrath
2004-06-24 18:10 ` Andrew Cagney
2004-06-24 20:59 ` Roland McGrath
2004-06-24 21:20 ` Mark Kettenis
2004-05-17 20:10 ` Andrew Cagney
[not found] ` <20040517131914.332fa347@saguaro>
2004-05-18 5:59 ` Eli Zaretskii
2004-05-18 20:09 ` Andrew Cagney
2004-05-19 5:50 ` Eli Zaretskii
2004-05-19 14:47 ` Andrew Cagney
2004-05-19 21:10 ` Eli Zaretskii
2004-05-20 5:33 ` Eli Zaretskii
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=40A0E813.2050803@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=roland@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