From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: drow@false.org, gdb-patches@sources.redhat.com, roland@redhat.com
Subject: Re: [obish?sym;rfa:doc] Wire up vsyscall
Date: Sat, 15 May 2004 20:58:00 -0000 [thread overview]
Message-ID: <200405152057.i4FKvdt2000817@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <40A16FA1.9060506@gnu.org>
Date: Tue, 11 May 2004 20:28:17 -0400
From: Andrew Cagney <cagney@gnu.org>
Another [SIGTRAMP_FRAME] attribute is how to display it when doing a
backtrace or stop.
I'm somewhat reluctant to throw the CFI completely overboard. How
about extending the DWARF2 unwinder such that we can set the
[SIGTRAMP_FRAME] attribute based on the function's name?
Mark
next prev parent reply other threads:[~2004-05-15 20:58 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
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 [this message]
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=200405152057.i4FKvdt2000817@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--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