Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270212AbTHQO2L (ORCPT ); Sun, 17 Aug 2003 10:28:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270222AbTHQO2K (ORCPT ); Sun, 17 Aug 2003 10:28:10 -0400 Received: from natsmtp00.webmailer.de ([192.67.198.74]:53182 "EHLO post.webmailer.de") by vger.kernel.org with ESMTP id S270212AbTHQO2J (ORCPT ); Sun, 17 Aug 2003 10:28:09 -0400 Message-ID: <3F3F913D.2090005@softhome.net> Date: Sun, 17 Aug 2003 16:29:17 +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: Alan Cox 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: 1087 Lines: 26 Alan Cox wrote: >> >> I do not see how it relates to abends. >> It logs _everything_, what is not that useful. Having some kind of >>filter what to log - whould be just great. Or alternatively ability to >>pass file descriptor - not file name. > > > It generates a small record for each exit, its trivial to parse the exit > codes for exits caused by an exception. > Silly question. Related. Is it possible to make kernel to print oops when SIGSEGV/SIGILL is registered, but execution was in kernel space? I'm not sure about current status - but this /feature/ was advertised for Linux kernels: when we have a crash in kernel space e.g. in sytem call that calling user space application which will crash. And no notice about the fact, that it was actually crash inside of Linux kernel. Am I right or am I wrong? - 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/