From: John Blackwood <john.blackwood@ccur.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, dan@debian.org, bugsy@ccur.com
Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
Date: Sat, 04 Jun 2005 09:03:04 -0400 [thread overview]
Message-ID: <42A1A688.7050505@ccur.com> (raw)
In-Reply-To: <d7q7jf$2s8$1@trex.ccur.com>
> Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
> From: Andrew Morton <akpm@osdl.org>
> Date: Fri, 3 Jun 2005 16:31:29 -0700
> To: Daniel Jacobowitz <dan@debian.org>
> CC: john.blackwood@ccur.com
>
> >>> >
> >>> > 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.
> >
> >>
> >> I'm not sure of the timeline, but could you check that in a current
> >> 2.6.12 GIT snapshot?
> >>
>
>
> 2.6.12-rc5 should be sufficient.
>
>
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.12-rc5.tar.bz2
>
> or, even better, the above plus:
>
>
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.12-rc5-git8.bz2
Andrew and Dan,
Yes, I tried the above combination, and the stuck-in-single-step mode
after continuing out of the signal handler is indeed FIXED.
Some additional code was added to the i386 version of handle_signal()
(even before the git8 additions) so that the TF flag is now cleared and
the task no longer stops when it comes out of the signal handler and
returns back to the original execution stream.
Thanks.
next parent reply other threads:[~2005-06-04 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d7q7jf$2s8$1@trex.ccur.com>
2005-06-04 13:03 ` John Blackwood [this message]
2005-06-06 12:54 [PATCH] ptrace(2) single-stepping into signal handlers John Blackwood
-- strict thread matches above, loose matches on Subject: below --
2005-06-03 18:07 John Blackwood
2005-06-03 18:11 ` Daniel Jacobowitz
2005-06-03 17:21 John Blackwood
2005-06-03 17:34 ` Daniel Jacobowitz
2005-06-05 11:21 ` Andi Kleen
2005-06-05 14:37 ` cutaway
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=42A1A688.7050505@ccur.com \
--to=john.blackwood@ccur.com \
--cc=akpm@osdl.org \
--cc=bugsy@ccur.com \
--cc=dan@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox