Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275308AbTHSCoG (ORCPT ); Mon, 18 Aug 2003 22:44:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275310AbTHSCoG (ORCPT ); Mon, 18 Aug 2003 22:44:06 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:65291 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S275308AbTHSCoE (ORCPT ); Mon, 18 Aug 2003 22:44:04 -0400 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: Dumb question: Why are exceptions such as SIGSEGV not logged Date: 18 Aug 2003 19:43:23 -0700 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: <3F3EB8FA.1080605@sktc.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2003 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 929 Lines: 23 Followup to: By author: "David Schwartz" In newsgroup: linux.dev.kernel > > There is no mechanism that is guaranteed to terminate a process other than > sending yourself an exception that is not caught. So in cases where you must > guarantee that your process terminates, it is perfectly reasonable to send > yourself a SIGILL. > exit(2)? -hpa -- at work, in private! If you send me mail in HTML format I will assume it's spam. "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/