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 [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
