Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275219AbTHRWjW (ORCPT ); Mon, 18 Aug 2003 18:39:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275234AbTHRWjW (ORCPT ); Mon, 18 Aug 2003 18:39:22 -0400 Received: from mail.webmaster.com ([216.152.64.131]:55515 "EHLO shell.webmaster.com") by vger.kernel.org with ESMTP id S275219AbTHRWjV (ORCPT ); Mon, 18 Aug 2003 18:39:21 -0400 From: "David Schwartz" To: "Mike Fedyk" , "Hank Leininger" Cc: Subject: RE: Dumb question: Why are exceptions such as SIGSEGV not logged Date: Mon, 18 Aug 2003 15:39:15 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <20030818210238.GG10320@matchmail.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 947 Lines: 28 > And why not just catch the ones sent from the kernel? That's the one that > is killing the program because it crashed, and that's the one the > origional > poster wants logged... Because sometimes a program wants to terminate. And it is perfectly legal for a programmer who needs to terminate his program as quickly as possible to do this: char *j=NULL; signal(SIGSEGV, SIG_DFL); *j++; This is a perfectly sensible thing for a program to do with well-defined semantics. If a program wants to create a child every minute like this and kill it, that's perfectly fine. We should be able to do that in the default configuration without a sysadmin complaining that we're DoSing his syslogs. DS - 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/