linux-mips
[Top] [All Lists]

Re: unkillable process due to setup_frame() failure

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: unkillable process due to setup_frame() failure
From: Ralf Baechle <ralf@linux-mips.org>
Date: Wed, 7 Sep 2005 17:11:57 +0100
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.61L.0509071619120.4591@blysk.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050906184118.GC3102@linux-mips.org> <Pine.LNX.4.61L.0509071011560.4591@blysk.ds.pg.gda.pl> <20050907134717.GA3493@linux-mips.org> <20050907.234413.108737010.anemo@mba.ocn.ne.jp> <Pine.LNX.4.61L.0509071619120.4591@blysk.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.2.1i
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

<Prev in Thread] Current Thread [Next in Thread>