From: kt <kt1023@comcast.net>
To: linux-assembly@vger.kernel.org
Subject: Where to find register content after exception ?
Date: Sat, 10 Jul 2004 14:45:15 -0400 [thread overview]
Message-ID: <40F0393B.104@comcast.net> (raw)
Hi,
I would like to get hold of the machine state after my user space
exception handler has been invoked by the kernel.
I wonder whether this information is passed by the third argument if
this type of handler :
void (*sa_sigaction)(int, siginfo_t *, void *);
has been installed by sigaction (man sigaction doesn't tell me this).
The other possibility could be that the kernel deposits this information
somewhere on the user stack before invoking the handler. I wonder
whether this is indeed the case and whether someone has already come up
with a nice solution to access this data if it is available in this
form. Since this is possibly system dependent, let me mention that I'm
using linux-ppc32 version 2.6.6 running on a PowerMacG5.
Regards,
K. Timmler
reply other threads:[~2004-07-10 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40F0393B.104@comcast.net \
--to=kt1023@comcast.net \
--cc=linux-assembly@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).