This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa] Attach vsyscall support for GNU/Linux
- From: Mark Kettenis <kettenis at gnu dot org>
- To: cagney at gnu dot org
- Cc: drow at false dot org, gdb-patches at sources dot redhat dot com, ezannoni at redhat dot com
- Date: Mon, 1 Nov 2004 23:12:47 +0100 (CET)
- Subject: Re: [rfa] Attach vsyscall support for GNU/Linux
- References: <20041024185345.GB22700@nevyn.them.org> <200410242054.i9OKsjnl028328@elgar.sibelius.xs4all.nl> <20041024231636.GA21927@nevyn.them.org> <200410252212.i9PMCQhJ031724@elgar.sibelius.xs4all.nl> <417D81D5.1000206@gnu.org>
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