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> In-Reply-To: <20010108161854.A3547@mezcal.tue.le>; from thz@Lennartz-electronic.de on Mon, Jan 08, 2001 at 04:18:55PM %2B0100 References: <20010108161854.A3547@mezcal.tue.le>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010108155357.A68700>