From owner-freebsd-hackers Wed Dec 20 7:28:45 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 20 07:28:43 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from herd.plethora.net (herd.plethora.net [205.166.146.1]) by hub.freebsd.org (Postfix) with ESMTP id 68B4637B404 for ; Wed, 20 Dec 2000 07:28:37 -0800 (PST) Received: from guild.plethora.net (root@guild.plethora.net [205.166.146.8]) by herd.plethora.net (8.9.0/8.9.0) with ESMTP id JAA04469 for ; Wed, 20 Dec 2000 09:28:31 -0600 (CST) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.9.3/8.9.0) with ESMTP id JAA15116 for ; Wed, 20 Dec 2000 09:28:30 -0600 (CST) Message-Id: <200012201528.JAA15116@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: hackers@freebsd.org Subject: Re: Why not another style thread? (was Re: cvs commit: src/lib/libc/gen .. In-reply-to: Your message of "Wed, 20 Dec 2000 11:25:36 GMT." Date: Wed, 20 Dec 2000 09:28:30 -0600 Sender: seebs@plethora.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Aled Morris writes: >Shouldn't you use "kill(0, SIGSEGV)" ? Gratuitously verbose! raise(SIGSEGV); (To be fair, raise(SIGSEGV) is quite likely to just jump to the segfault handler without actually setting any signal bits, but who can tell?[*]) -s [*] I don't have a FreeBSD complete source tree handy, this is a general comment about arbitrary future libc implementations. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message