From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
Subject: Re: unkillable process due to setup_frame() failure
Date: Wed, 7 Sep 2005 17:11:57 +0100 [thread overview]
Message-ID: <20050907161157.GA11379@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0509071619120.4591@blysk.ds.pg.gda.pl>
On Wed, Sep 07, 2005 at 04:24:05PM +0100, Maciej W. Rozycki wrote:
> > So my "which is preferred" question was inappropriate. I had to ask
> > "#1 or #2 or both or other ?"
>
> We should be consistent with other platforms -- having a look at e.g. the
> i386 (as it used to be the reference) and the alpha (as close-enough to
> MIPS) should reveal the answer. IIRC, a SIGSEGV that has a handler
> installed, but which cannot be callled due to a bad stack pointer is
> forced to SIG_DFL, but you may want to double-check it.
That's what's already happening. We call force_sigsegv which is like
force_sig unless it's trying to deliver a SIGSEGV in which case it'll
reset the handler to SIG_DFL, return to userspace where it hits the
break instruction and starts all over to process the SIGTRAP.
Ralf
next prev parent reply other threads:[~2005-09-07 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 16:42 unkillable process due to setup_frame() failure Atsushi Nemoto
2005-09-06 18:41 ` Ralf Baechle
2005-09-07 9:14 ` Maciej W. Rozycki
2005-09-07 13:47 ` Ralf Baechle
2005-09-07 14:44 ` Atsushi Nemoto
2005-09-07 14:56 ` Atsushi Nemoto
2005-09-07 15:24 ` Maciej W. Rozycki
2005-09-07 16:11 ` Ralf Baechle [this message]
2005-09-07 16:34 ` Maciej W. Rozycki
2005-09-15 16:17 ` Atsushi Nemoto
2005-09-15 16:44 ` Ralf Baechle
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=20050907161157.GA11379@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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 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.