public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Michael Frank <mhf@linuxmail.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Dumb question: Why are exceptions such as SIGSEGV not logged
Date: Mon, 18 Aug 2003 07:31:46 -0700	[thread overview]
Message-ID: <20030818143146.GV32488@holomorphy.com> (raw)
In-Reply-To: <200308170410.30844.mhf@linuxmail.org>

On Sun, Aug 17, 2003 at 04:10:30AM +0800, Michael Frank wrote:
> Linux logs almost everything, why not exceptions such as SIGSEGV in
> userspace which may be very informative?

Such exceptions are part of the normal operation of certain kinds of
programs, such as ones using (nowadays unusual) certain garbage
collection algorithms. I actually installed such a beast (Lisp system)
in no small part so it would exercise "invalid" memory accesses and
test various bits of VM code related to such. For other VM people
interested in it, there's an sbcl debian package that recompiles a
moderately sized chunk of Lisp code and hence runs the system at
install-time, and so exercises the SIGSEGV path rather heavily on
32-bit systems and/or systems with <= 2GB of RAM. No particular
intervention apart from (re)installing it is required to pound the
SIGSEGV path like a wild monkey, so it's actually a very convenient
touch test for such things.


-- wli

  parent reply	other threads:[~2003-08-18 14:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-16 20:10 Dumb question: Why are exceptions such as SIGSEGV not logged 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 [this message]
2003-08-18 17:52   ` Michael Frank
     [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
  -- 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-18 20:50 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

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=20030818143146.GV32488@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox