From owner-freebsd-stable Tue Oct 16 20:37:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id E22B137B401 for ; Tue, 16 Oct 2001 20:37:32 -0700 (PDT) Received: (qmail 24686 invoked by uid 1001); 17 Oct 2001 13:37:29 +1000 Message-ID: X-Posted-By: GJB-Post 2.21 16-Jun-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Wed, 17 Oct 2001 13:37:29 +1000 From: Greg Black To: David Marker Cc: freebsd-stable@freebsd.org Subject: Re: SIGSEGV not blocked in gdm [was Re: setenv() cores with NULL value] References: <20011016164610.95419.qmail@web14702.mail.yahoo.com> In-reply-to: <20011016164610.95419.qmail@web14702.mail.yahoo.com> of Tue, 16 Oct 2001 09:46:10 MST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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