From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andrew Cagney <cagney@gnu.org>,
jim.houston@comcast.net, gdb-patches@sources.redhat.com
Subject: Re: [patch] allow switching stacks
Date: Mon, 12 Apr 2004 21:05:00 -0000 [thread overview]
Message-ID: <vt2lll07vv6.fsf@zenia.home> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2004-04-12 21:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:06 Jim Houston
2004-03-08 22:58 ` Michael Snyder
2004-03-19 0:09 ` Eli Zaretskii
2004-03-09 6:06 ` Eli Zaretskii
2004-03-19 0:09 ` Michael Snyder
2004-03-09 20:21 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-04-02 22:06 ` Andrew Cagney
2004-04-09 22:40 ` Daniel Jacobowitz
2004-04-12 21:05 ` Jim Blandy [this message]
2004-04-12 21:13 ` Daniel Jacobowitz
2004-03-19 0:09 ` Jim Houston
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=vt2lll07vv6.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jim.houston@comcast.net \
/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