This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch] allow switching stacks
- From: Jim Blandy <jimb at redhat dot com>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: Andrew Cagney <cagney at gnu dot org>, jim dot houston at comcast dot net, gdb-patches at sources dot redhat dot com
- Date: 12 Apr 2004 16:02:37 -0500
- Subject: Re: [patch] allow switching stacks
- References: <m3y8qbp650.fsf@new.localdomain> <404E2745.2090405@gnu.org><20040409215453.GA1090@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> There's no way in unwind information to annotate a non-call frame,
> which is the common relevant property for signal frames, dummy frames,
> and interrupt handler frames. Should there be?
There isn't? For signal frames, for example, the registers are all
saved in the ucontext_t, on the signal handler's stack. Can't we
hand-build Dwarf 2 CFI that points into the ucontext_t?
On IA-32 machines, the processor saves %eflags, %eip, and %cs, and
possibly %esp and %ss, and it's up to the handler code to save
whatever else needs preserving. We could hand-build Dwarf 2 CFI for
that, too.