From owner-freebsd-stable  Mon Jan  8  7:54:20 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by hub.freebsd.org (Postfix) with SMTP id 4FCE637B402
	for <freebsd-stable@freebsd.org>; Mon,  8 Jan 2001 07:54:02 -0800 (PST)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa22635@salmon>; 8 Jan 2001 15:53:58 +0000 (GMT)
Date: Mon, 8 Jan 2001 15:53:57 +0000
From: David Malone <dwmalone@maths.tcd.ie>
To: Thomas Zenker <thz@Lennartz-electronic.de>
Cc: freebsd-stable@freebsd.org
Subject: Re: SIGSEGV can be blocked!?
Message-ID: <20010108155357.A68700@walton.maths.tcd.ie>
References: <20010108161854.A3547@mezcal.tue.le>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010108161854.A3547@mezcal.tue.le>; from thz@Lennartz-electronic.de on Mon, Jan 08, 2001 at 04:18:55PM +0100
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Jan 08, 2001 at 04:18:55PM +0100, Thomas Zenker wrote:
> Blocking SIGSEGV with sigprocmask does really BLOCK it. 
> I think, this is a bug. I discovered this because I wanted to
> provoke a core dump by a write to (int *)0, but the process got hung,
> ps -ax showed it constantly running. A SIGQUIT got it to dump core and
> gdb showed exactly my write to NULL. Probably the process gets
> occupied by repeatedly retrying the write to null??

I think some programs catch signals for SIGSEGV and SIGBUS to do
memory management things, so this is expected. If you want your
program to core dump then call abort().

	David.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message