mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Andi Kleen <ak@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, plars@austin.ibm.com,
	akpm@digeo.com
Subject: Re: [PATCH] Exception trace for i386
Date: Tue, 20 May 2003 13:17:17 +0200	[thread overview]
Message-ID: <20030520131717.J626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <p73k7cmzl7d.fsf@oldwotan.suse.de>; from ak@suse.de on Mon, May 19, 2003 at 11:21:42PM +0200

On Mon, May 19, 2003 at 11:21:42PM +0200, Andi Kleen wrote:
> I especially like it being a global option. It has catched bugs on x86-64 
> that were never noticed before (e.g. subprocesses silently segfaulting 
> that nobody noticed doing the same on i386). Clearly it's an debugging 
> thing and you definitely want an option to turn it off. But having 
> the global option is useful.

Would you consider doing the logging only, if the process has no
real handler for that? (so it's blocking, ignoring or not caring
about this signal)

This will reveal only the bugs and not disturb the applications,
which do sth. useful with segfaults.

Regards

Ingo Oeser

  reply	other threads:[~2003-05-20 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030519192814.GA975@averell.suse.lists.linux.kernel>
     [not found] ` <1053377808.588720@palladium.transmeta.com.suse.lists.linux.kernel>
2003-05-19 21:21   ` Andi Kleen
2003-05-20 11:17     ` Ingo Oeser [this message]
2003-05-20 12:11       ` Andi Kleen
2003-05-19 19:28 Andi Kleen
2003-05-19 20:56 ` Linus Torvalds
2003-05-19 22:24   ` Alan Cox

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=20030520131717.J626@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=ak@suse.de \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plars@austin.ibm.com \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®