From owner-freebsd-hackers Wed Feb 19 18: 8: 3 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDDB737B401 for ; Wed, 19 Feb 2003 18:08:01 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BCED43F75 for ; Wed, 19 Feb 2003 18:08:01 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0147.cvx21-bradley.dialup.earthlink.net ([209.179.192.147] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18lg76-0005ls-00; Wed, 19 Feb 2003 18:07:05 -0800 Message-ID: <3E5437CB.DC14EC42@mindspring.com> Date: Wed, 19 Feb 2003 18:04:59 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Vaclav Haisman Cc: freebsd-hackers@freebsd.org Subject: Re: Raising SIGSEGV in SIGSEGV handler makes FreeBSD loop References: <20030219134131.T70370-100000@logout.sh.cvut.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a44b846b20a6acf701444c40ff6b0759732601a10902912494350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vaclav Haisman wrote: > > man 2 abort > > > > -- Terry > > logout ~/tmp>man 2 abort > No entry for abort in section 2 of the manual > > Besides, this doesn't explain anything. I see I haven't asked any question in > my previous post. So, why does FreeBSD behave different? Because POSIX mandates that it do so? man 3 signal tells us: The handled signal is unblocked when the function returns and the process continues from where it left off when the signal occurred. Unlike previ- ous signal facilities, the handler func() remains installed after a sig- nal has been delivered. If you want this to not happen, you should explicitly uninstall the handler, or you should call abort(3) (or _exit(2), if you don't want to leave a core dump). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message