From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: James.Bottomley@SteelEye.com,
parisc-linux@lists.parisc-linux.org, tsg45800@scarlet.be
Subject: Re: [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1
Date: Wed, 17 Aug 2005 07:57:39 +0800 [thread overview]
Message-ID: <43027D73.80906@tausq.org> (raw)
In-Reply-To: <200508161339.j7GDdqw9024211@hiauly1.hia.nrc.ca>
>>Is the kernel responsible for blocking SIGSEGV handlers that generate
>>SIGSEGV?
>
> See http://www.opengroup.org/onlinepubs/009695399/functions/signal.html.
>
> This is implementation defined.
James spotted where we were not doing the right thing when setting up a
signal handler frame. I've checked in his suggested fix to
2.6.13-rc6-pa2. I think it should solve the problem.
randolph
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-08-16 23:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 9:17 [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1 Joel Soete
2005-08-16 10:10 ` Randolph Chung
2005-08-16 13:39 ` John David Anglin
2005-08-16 14:34 ` Randolph Chung
2005-08-16 15:06 ` Michael S. Zick
2005-08-16 23:57 ` Randolph Chung [this message]
2005-08-17 0:08 ` John David Anglin
2005-08-17 0:50 ` John David Anglin
[not found] <no.id>
2005-08-16 3:32 ` John David Anglin
[not found] <20050812180551.GA32609@colo.lackof.org>
2005-08-13 0:00 ` John David Anglin
2005-08-13 5:02 ` Grant Grundler
2005-08-13 5:11 ` John David Anglin
2005-08-13 5:14 ` John David Anglin
2005-08-13 13:40 ` James Bottomley
2005-08-13 17:46 ` John David Anglin
2005-08-13 19:30 ` John David Anglin
2005-08-16 3:02 ` Randolph Chung
2005-08-16 3:18 ` John David Anglin
2005-08-14 1:32 ` John David Anglin
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=43027D73.80906@tausq.org \
--to=randolph@tausq.org \
--cc=James.Bottomley@SteelEye.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tsg45800@scarlet.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.