From: <cutaway@bellsouth.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
Date: Sun, 5 Jun 2005 10:37:29 -0400 [thread overview]
Message-ID: <007e01c569dc$1d6d2160$2800000a@pc365dualp2> (raw)
In-Reply-To: 20050605112119.GU23831@wotan.suse.de
----- Original Message -----
From: "Andi Kleen" <ak@suse.de>
To: "John Blackwood" <john.blackwood@ccur.com>
Cc: <linux-kernel@vger.kernel.org>; <roland@redhat.com>; <ak@suse.de>;
<akpm@osdl.org>; <bugsy@ccur.com>
Sent: Sunday, June 05, 2005 07:21
Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
> On Fri, Jun 03, 2005 at 01:21:20PM -0400, John Blackwood wrote:
> > 1. Make the default behavior that we single-step to the next instruction
> > in the main (non-signal handler) stream of execution, instead of
> > single-stepping into the user's signal handler.
>
> I think it is better to not change the default behaviour. You risk
> breaking programs and there are much more that use ptrace than just gdb.
A performance trace profiler would want to step through signal handlers.
Sometimes they're an architected norm for a program rather than an abnormal
condition handler (ex. Lisp systems routinely handling GP faults on null
pointers rather than doing null pointer checks in critical loops)
next prev parent reply other threads:[~2005-06-05 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 17:21 [PATCH] ptrace(2) single-stepping into signal handlers John Blackwood
2005-06-03 17:34 ` Daniel Jacobowitz
2005-06-05 11:21 ` Andi Kleen
2005-06-05 14:37 ` cutaway [this message]
2005-06-03 18:07 John Blackwood
2005-06-03 18:11 ` Daniel Jacobowitz
[not found] <d7q7jf$2s8$1@trex.ccur.com>
2005-06-04 13:03 ` John Blackwood
2005-06-06 12:54 John Blackwood
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='007e01c569dc$1d6d2160$2800000a@pc365dualp2' \
--to=cutaway@bellsouth.net \
--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.