Date: Wed, 17 Oct 2001 13:37:29 +1000 From: Greg Black <gjb@gbch.net> To: David Marker <marker_d@yahoo.com> Cc: freebsd-stable@freebsd.org Subject: Re: SIGSEGV not blocked in gdm [was Re: setenv() cores with NULL value] Message-ID: <nospam-1003289849.24685@mx1.gbch.net> In-Reply-To: <20011016164610.95419.qmail@web14702.mail.yahoo.com> of Tue, 16 Oct 2001 09:46:10 MST References: <20011016164610.95419.qmail@web14702.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Marker wrote: | Before reading that I was not aware you could block | a SIGSEGV. But gdm doesn't even appear to block that | signal. (grep for sigation, then SIGSEGV, didn't find | anything to suggest it blocks SIGSEGV.) This is not by any means a reliable method of finding out if a signal is blocked: sigaction (not sigation) is not the only interface for setting signal handlers, etc; people often just use the integer values rather than the special constants; other factors might come into play. 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?nospam-1003289849.24685>