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>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010108161854.A3547>