From: Andi Kleen <ak@suse.de>
To: Sean Kamath <skamath@anim.dreamworks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about Kernel Reporting Sigfaults in <arch>/mm/fault.c
Date: 07 Jul 2006 14:19:31 +0200 [thread overview]
Message-ID: <p73bqs1ppyk.fsf@verdi.suse.de> (raw)
In-Reply-To: <44AD8E1F.2020509@anim.dreamworks.com>
Sean Kamath <skamath@anim.dreamworks.com> writes:
>
> exception_trace is set to 1 (line 296) and not used anywhere else in the file.
>
It can be set using /proc/sys/debug/exception-trace
> The question(s): Is this intentional (to have segfaults reported on x86_64,
Yes.
> I admit, it would be nice to be able to toggle on and off segfault
> reporting in the kernel (from a system administration point of view, this
> is helpful to be able to go back to developers and say 'your program is
> crashing a lot' -- something necessary if you are protecting end-users from
> a lot of core files . . .) on all platforms.
It was originally was added when the port was still young to debug user
land faster, but it keeps people honest and is still very useful.
In fact it found some long standing bugs that were never noticed on i386 with
programs silently segfaulting.
-Andi
prev parent reply other threads:[~2006-07-07 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 22:26 Question about Kernel Reporting Sigfaults in <arch>/mm/fault.c Sean Kamath
2006-07-07 12:19 ` Andi Kleen [this message]
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=p73bqs1ppyk.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=skamath@anim.dreamworks.com \
/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