Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S274968AbTHPVmn (ORCPT ); Sat, 16 Aug 2003 17:42:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S274975AbTHPVmn (ORCPT ); Sat, 16 Aug 2003 17:42:43 -0400 Received: from mail.jlokier.co.uk ([81.29.64.88]:56450 "EHLO mail.jlokier.co.uk") by vger.kernel.org with ESMTP id S274968AbTHPVml (ORCPT ); Sat, 16 Aug 2003 17:42:41 -0400 Date: Sat, 16 Aug 2003 22:42:37 +0100 From: Jamie Lokier To: Valdis.Kletnieks@vt.edu Cc: Michael Frank , linux-kernel Subject: Re: Dumb question: Why are exceptions such as SIGSEGV not logged Message-ID: <20030816214237.GB25483@mail.jlokier.co.uk> References: <200308170410.30844.mhf@linuxmail.org> <200308162049.h7GKnwnP024716@turing-police.cc.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308162049.h7GKnwnP024716@turing-police.cc.vt.edu> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 18 Valdis.Kletnieks@vt.edu wrote: > On Sun, 17 Aug 2003 04:10:30 +0800, Michael Frank said: > > Linux logs almost everything, why not exceptions such as SIGSEGV > > in userspace which may be very informative? > > [SIG_IGN] Presumably only SIGSEGVs which kill a process would be logged... Some programs actually _use_ SIGSEGV in a useful way, to manage memory. Same for SIGBUS and other signals. It would be wrong to log them. -- Jamie - 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/