From owner-freebsd-stable  Mon Jan  8  7:19:41 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.tue.le (p3EE3268C.dip.t-dialin.net [62.227.38.140])
	by hub.freebsd.org (Postfix) with ESMTP id 5509A37B402
	for <freebsd-stable@freebsd.org>; Mon,  8 Jan 2001 07:19:19 -0800 (PST)
Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20])
	by mail.tue.le (8.8.8/8.8.8) with ESMTP id QAA25864
	for <freebsd-stable@freebsd.org>; Mon, 8 Jan 2001 16:18:55 +0100 (CET)
	(envelope-from thz@mezcal.tue.le)
Received: (from thz@localhost)
	by mezcal.tue.le (8.11.1/8.11.1) id f08FItr05939
	for freebsd-stable@freebsd.org; Mon, 8 Jan 2001 16:18:55 +0100 (CET)
	(envelope-from thz)
Date: Mon, 8 Jan 2001 16:18:55 +0100
From: Thomas Zenker <thz@Lennartz-electronic.de>
To: freebsd-stable@freebsd.org
Subject: SIGSEGV can be blocked!?
Message-ID: <20010108161854.A3547@mezcal.tue.le>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

debugging a program I discovered a strange behaviour today:

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

this is on 4.2-STABLE from 21 of december

any opinions?


-- Thomas Zenker
   c/o Lennartz electronic GmbH
   Bismarckstrasse 136, D-72072 Tuebingen, Germany
   Phone:  +49-(0)7071-93550
   Email:  thz@lennartz-electronic.de


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