From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Dumb question: Why are exceptions such as SIGSEGV not logged
Date: Sun, 17 Aug 2003 16:29:17 +0200 [thread overview]
Message-ID: <3F3F913D.2090005@softhome.net> (raw)
In-Reply-To: <lvC1.3p9.11@gated-at.bofh.it>
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?
next parent reply other threads:[~2003-08-17 14:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <lv8Y.2XU.9@gated-at.bofh.it>
[not found] ` <lv8Y.2XU.11@gated-at.bofh.it>
[not found] ` <lv8Y.2XU.13@gated-at.bofh.it>
[not found] ` <lviD.35d.3@gated-at.bofh.it>
[not found] ` <lviD.35d.1@gated-at.bofh.it>
[not found] ` <lvC1.3p9.11@gated-at.bofh.it>
2003-08-17 14:29 ` Ihar 'Philips' Filipau [this message]
2003-08-18 20:50 Dumb question: Why are exceptions such as SIGSEGV not logged Hank Leininger
2003-08-18 21:02 ` Mike Fedyk
2003-08-18 21:18 ` Hank Leininger
2003-08-18 21:25 ` Mike Fedyk
2003-08-18 22:12 ` William Lee Irwin III
2003-08-18 22:39 ` David Schwartz
2003-08-18 22:44 ` Mike Fedyk
2003-08-18 22:53 ` David Schwartz
2003-08-19 6:54 ` Denis Vlasenko
2003-08-19 14:52 ` Valdis.Kletnieks
2003-08-19 18:51 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2003-08-18 1:56 Hank Leininger
[not found] <lg0i.6yo.11@gated-at.bofh.it>
[not found] ` <lgjJ.6Oo.5@gated-at.bofh.it>
[not found] ` <lilr.p2.7@gated-at.bofh.it>
[not found] ` <livc.wX.17@gated-at.bofh.it>
2003-08-17 12:43 ` Ihar 'Philips' Filipau
[not found] ` <lj7O.14a.1@gated-at.bofh.it>
2003-08-17 12:52 ` Ihar 'Philips' Filipau
2003-08-17 13:09 ` Alan Cox
[not found] ` <lOll.3Jp.19@gated-at.bofh.it>
2003-08-18 9:34 ` Ihar 'Philips' Filipau
2003-08-18 17:26 ` David Schwartz
2003-08-16 20:10 Michael Frank
2003-08-16 20:49 ` Valdis.Kletnieks
2003-08-16 21:42 ` Jamie Lokier
2003-08-16 23:06 ` David D. Hagood
2003-08-16 23:17 ` Doug McNaught
2003-08-16 23:41 ` Dr. David Alan Gilbert
2003-08-17 8:17 ` Russell King
2003-08-16 23:49 ` Alan Cox
2003-08-17 20:54 ` Jakob Oestergaard
2003-08-18 4:28 ` Michael Frank
2003-08-18 9:15 ` David Schwartz
2003-08-19 2:43 ` H. Peter Anvin
2003-08-19 13:27 ` Jesse Pollard
2003-08-19 19:28 ` David Schwartz
2003-08-19 19:34 ` H. Peter Anvin
2003-08-19 20:01 ` David Schwartz
2003-08-18 14:31 ` William Lee Irwin III
2003-08-18 17:52 ` Michael Frank
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F3F913D.2090005@softhome.net \
--to=filia@softhome.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.