From: Daniel Barlow <dan@telent.net>
To: Camm Maguire <camm@enhanced.com>,
debian-alpha <debian-alpha@lists.debian.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: SA_SIGINFO in Linux 2.4.x
Date: Fri, 02 Aug 2002 13:41:35 +0100 [thread overview]
Message-ID: <87k7n9l9fk.fsf@noetbook.telent.net> (raw)
In-Reply-To: <1028281936.17352.42.camel@satan.xko.dec.com> ("Aneesh Kumar K.V"'s message of "02 Aug 2002 15:22:16 +0530")
On Fri, 2002-08-02 at 04:14, Camm Maguire wrote:
> Greetings! The 2.4.x kernels on alpha don't appear to be filling in
> the si_addr element of the siginfo_t structure when a signal handler
> is setup with SA_SIGINFO. Is this right? Any other way to get this
> address in the handler?
You may be able to use the third argument to the signal handler:
given a handler declared as (int n, siginfo_t *info,struct ucontext *context),
look at context->uc_mcontext.sc_traparg_a0
SBCL has been doing this for a few months now and nobody has yet
complained that it's broken for them. Look for arch_get_bad_addr
in http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/sbcl/sbcl/src/runtime/alpha-arch.c?rev=1.14&content-type=text/vnd.viewcvs-markup
-dan
--
http://ww.telent.net/cliki/ - Link farm for free CL-on-Unix resources
next prev parent reply other threads:[~2002-08-02 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17aOg0-0002ub-00@intech19.enhanced.com>
2002-08-02 9:52 ` SA_SIGINFO in Linux 2.4.x Aneesh Kumar K.V
2002-08-02 12:41 ` Daniel Barlow [this message]
2002-08-02 15:54 ` Camm Maguire
2002-08-02 16:01 ` [Gcl-devel] " Camm Maguire
2002-08-02 21:36 ` Goswin Brederlow
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=87k7n9l9fk.fsf@noetbook.telent.net \
--to=dan@telent.net \
--cc=camm@enhanced.com \
--cc=debian-alpha@lists.debian.org \
--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