From: Mark Kettenis <kettenis@gnu.org>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com, cagney@gnu.org
Subject: Re: [rfa] Attach vsyscall support for GNU/Linux
Date: Sun, 24 Oct 2004 20:55:00 -0000 [thread overview]
Message-ID: <200410242054.i9OKsjnl028328@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20041024185345.GB22700@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 24 Oct 2004 14:53:45 -0400)
Date: Sun, 24 Oct 2004 14:53:45 -0400
From: Daniel Jacobowitz <drow@false.org>
This patch, based on a patch Andrew posted earlier this year, connects
vsyscall support to the inferior_created observer.
As before, I have adjusted the i386-linux sigtramp code to recognize
the names of the kernel trampolines (both of them this time - I forgot
the RT case when I first did this). And I have adjusted the i386
target to recognize signal trampolines before searching for DWARF-2
unwind information, as previously discussed. Other architectures which
now have a vsyscall DSO may need to make the same change.
I still don't get it. What exactly was the purpose of adding the
vsyscall DSO if we're not using the DWARF CFI it contains. Can't the
people who dreamt up this wonderful mechanism fix their implementation
such that it doesn't contain any useless DWARF CFI? I'm a bit
reluctant to approve this since it'll probably mean that it never get
fixed properly :-(.
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...
Mark
next prev parent reply other threads:[~2004-10-24 20:55 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 [this message]
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
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=200410242054.i9OKsjnl028328@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.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