From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>, Mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com,
Roland McGrath <roland@redhat.com>
Subject: Re: [rfa] Attach vsyscall support for GNU/Linux
Date: Mon, 25 Oct 2004 22:54:00 -0000 [thread overview]
Message-ID: <417D83BB.3070706@gnu.org> (raw)
In-Reply-To: <20041024231636.GA21927@nevyn.them.org>
>>But there's another reason why I'm against this patch. It changes the
>>order of the unwinders for all the other i386 targets too. Please
>>find a way to do this such that it affect Linux only.
>>
>>Sorry, I didn't realize this before...
I'd not get too hung up on this one. The current frame-unwind code
sniff heuristic came about because it ``worked for me''. We're going
to have to eventually replace it with something more complicated and
until then, what ever.
Sniffing a signal frame definitly takes higher priority than sniffing a
normal frame.
> OK, if the rest of the patch reaches consensus I will try to figure out
> how to do this. It will probably just require conditional action based
> on the osabi enum. Not hard.
Andrew
next prev parent reply other threads:[~2004-10-25 22:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 18:53 Daniel Jacobowitz
2004-10-24 20:55 ` Mark Kettenis
2004-10-24 23:16 ` Daniel Jacobowitz
2004-10-25 22:12 ` Mark Kettenis
2004-10-25 22:46 ` Andrew Cagney
2004-11-01 22:13 ` Mark Kettenis
2004-11-02 14:28 ` Andrew Cagney
2004-11-01 16:15 ` Daniel Jacobowitz
2004-11-01 20:45 ` Mark Kettenis
2004-11-01 22:32 ` Daniel Jacobowitz
2004-11-02 14:29 ` Andrew Cagney
2004-11-07 21:35 ` Daniel Jacobowitz
2004-11-08 16:40 ` Andrew Cagney
2004-11-05 23:42 ` Daniel Jacobowitz
2004-11-07 17:36 ` Mark Kettenis
2004-11-07 21:18 ` Daniel Jacobowitz
2004-11-07 21:34 ` Mark Kettenis
2004-10-25 22:54 ` Andrew Cagney [this message]
2004-10-26 2:51 ` Roland McGrath
2004-10-26 8:17 ` Jakub Jelinek
2004-10-26 13:27 ` Daniel Jacobowitz
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=417D83BB.3070706@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.org \
--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