linux-mips
[Top] [All Lists]

Re: unkillable process due to setup_frame() failure

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: unkillable process due to setup_frame() failure
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Wed, 7 Sep 2005 17:34:57 +0100 (BST)
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
In-reply-to: <20050907161157.GA11379@linux-mips.org>
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> <20050907161157.GA11379@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
On Wed, 7 Sep 2005, Ralf Baechle wrote:

> 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.

 Except that SIG_DFL for SIGSEGV is killing the process (with a core 
dump).  Therefore user space shouldn't ever be reached again in this 
context.

  Maciej

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