From: Orjan Friberg <orjan.friberg@axis.com>
To: linux-kernel@vger.kernel.org
Cc: orjan.friberg@axis.com
Subject: sa_sigaction signal handler: third parameter?
Date: Wed, 05 Sep 2001 11:58:29 +0200 [thread overview]
Message-ID: <3B95F745.A1476AFD@axis.com> (raw)
I'm trying to make life easier for a user-defined SIGSEGV handler, the
sa_sigaction one with 3 parameters. The second parameter, the siginfo_t
* one, is there. Problem is, I would like to pass on additional
information to the signal handler, more specifically information about
whether there was a protection fault, read/write etc. I've looked at
some of the other ports (I'm working on the CRIS port BTW), and for
example the i386 has fields in the task and sigcontext structs to keep
this sort of information.
Question is how to pass this information on to the signal handler.
Looking at the code, it seems the third parameter (void *) is being used
to send a ucontext_t * in (at least) the arm and mips cases. I followed
a lot of threads in the archive, but couldn't find one that adressed
what this third parameter is actually meant to be used for. Obviously,
sending a ucontext would solve my problem, since it contains the
sigcontext struct. Is there a Right Way to do it?
(I'm not subscribed to the list, so please keep me on the CC list.)
--
Orjan Friberg E-mail: orjan.friberg@axis.com
Axis Communications AB Phone: +46 46 272 17 68
next reply other threads:[~2001-09-05 9:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 9:58 Orjan Friberg [this message]
2001-09-07 1:38 ` sa_sigaction signal handler: third parameter? Jamie Lokier
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=3B95F745.A1476AFD@axis.com \
--to=orjan.friberg@axis.com \
--cc=linux-kernel@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