Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269509AbTHQMma (ORCPT ); Sun, 17 Aug 2003 08:42:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269578AbTHQMma (ORCPT ); Sun, 17 Aug 2003 08:42:30 -0400 Received: from natsmtp01.webmailer.de ([192.67.198.81]:24566 "EHLO post.webmailer.de") by vger.kernel.org with ESMTP id S269509AbTHQMm3 (ORCPT ); Sun, 17 Aug 2003 08:42:29 -0400 Message-ID: <3F3F7878.1000202@softhome.net> Date: Sun, 17 Aug 2003 14:43:36 +0200 From: "Ihar 'Philips' Filipau" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug McNaught CC: Linux Kernel Mailing List Subject: Re: Dumb question: Why are exceptions such as SIGSEGV not logged References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 896 Lines: 24 Doug McNaught wrote: > > You can still DoS by forking repeatedly and having the child die with > SEGV... > We had a problems with synchronization between CPU and memory. But the problem was showing up us random crashes of applications with SIGSEGV and (rarely) SIGILL. But still to prove bug is not in Linux kernel and not in software we have killed three weeks, just to find out that Motorola has forgotten to publish one errata for their CPU. Probably to have an option to log this kind of signals would be useful. Because just blindly killing applications - is not correct too. I will vote for 'if unhandled -> log it' ;-) - 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/