From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: drow@false.org, gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [rfa] Attach vsyscall support for GNU/Linux
Date: Mon, 01 Nov 2004 22:13:00 -0000 [thread overview]
Message-ID: <200411012212.iA1MClCE000632@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <417D81D5.1000206@gnu.org> (message from Andrew Cagney on Mon, 25 Oct 2004 18:44:37 -0400)
Date: Mon, 25 Oct 2004 18:44:37 -0400
From: Andrew Cagney <cagney@gnu.org>
Thos funny little diagrams are UML isn't it?
It needs to be changed so more like:
SYMBOL
/|\
|
FRAME <>----- FUNCTION <>------ UNWINDER
and have the FUNCTION provide:
- signal trampoline?
I think this is wrong. It's probably true that functions that are
used as signal trampolines in traditional UNIX systems are only usable
as such, this is not true for interrupt handlers. On i386 systems you
can write interrupt handlers that are also usable as trap handlers.
Where interrupt handlers are sigtramp-like, trap handlers are musch
more normal. This kind of attributes depend more on the context and
thereforeit is more logical to put them in the frame. I think the
same is true for the unwinder.
That said, it is perfectly reasonable to let the frame inherit some of
these attributes from the function.
Mark
next prev parent reply other threads:[~2004-11-01 22:13 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 [this message]
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=200411012212.iA1MClCE000632@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