Skip to contentSkip to conversation

ptrace(2) single-stepping into signal handlers

PATCH John Blackwood 2 participants 2 messages Jun 3, 2005

lore
Share & tools
lore
#0 lore raw
Quoted 8 lines

Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
From: Daniel Jacobowitz <[email protected]>
Date: Fri, 3 Jun 2005 13:34:33 -0400
To: John Blackwood <[email protected]>
CC: [email protected], [email protected], [email protected], [email protected], [email protected]

On Fri, Jun 03, 2005 at 01:21:20PM -0400, John Blackwood wrote:

Quoted 8 lines
Quoted 4 lines
Quoted 4 lines

The reason for this behavior is due to the fact that:

- We saved off the eflags (with the TF bit set) in setup_sigcontext() before we single stepped into the user's signal handler.

You didn't say what kernel you were using. I believe this was fixed some time ago.

Hi Dan,

I observed this behavior in a 2.6.11.10 kernel. The code in 2.6.11.11 looks the same in this area... this is the i386 code that I am speaking of.

I guess that 'some time ago' is more recent than that?

If so, then please excuse me... and it's great that this is fixed.

#1 lore raw
Quoted 20 lines · John Blackwood
Quoted 5 lines

Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
From: Daniel Jacobowitz <[email protected]>
Date: Fri, 3 Jun 2005 13:34:33 -0400
To: John Blackwood <[email protected]>
CC: [email protected], [email protected], [email protected],

[email protected], [email protected]

Quoted 11 lines · John Blackwood
Quoted 5 lines
Quoted 5 lines

The reason for this behavior is due to the fact that:

- We saved off the eflags (with the TF bit set) in setup_sigcontext() before we single stepped into the user's signal handler.

You didn't say what kernel you were using. I believe this was fixed some time ago.

Hi Dan,

Quoted 7 lines

I observed this behavior in a 2.6.11.10 kernel. The code in 2.6.11.11 looks the same in this area... this is the i386 code that I am speaking of.

I guess that 'some time ago' is more recent than that?

If so, then please excuse me... and it's great that this is fixed.

I'm not sure of the timeline, but could you check that in a current 2.6.12 GIT snapshot?

Signature · 2 lines
Daniel Jacobowitz
CodeSourcery, LLC