Re: [PATCH] ptrace(2) single-stepping into signal handlers

[cutaway]

----- Original Message ----- 
From: "Andi Kleen" <ak@xxxxxxx>
To: "John Blackwood" <john.blackwood@xxxxxxxx>
Cc: <linux-kernel@xxxxxxxxxxxxxxx>; <roland@xxxxxxxxxx>; <ak@xxxxxxx>;
<akpm@xxxxxxxx>; <bugsy@xxxxxxxx>
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)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/