From: Daniel Jacobowitz <dan@debian.org>
To: John Blackwood <john.blackwood@ccur.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
Date: Fri, 3 Jun 2005 14:11:06 -0400 [thread overview]
Message-ID: <20050603181106.GB29940@nevyn.them.org> (raw)
In-Reply-To: <42A09C6C.8030104@ccur.com>
On Fri, Jun 03, 2005 at 02:07:40PM -0400, John Blackwood wrote:
> > Subject: Re: [PATCH] ptrace(2) single-stepping into signal handlers
> > From: Daniel Jacobowitz <dan@debian.org>
> > Date: Fri, 3 Jun 2005 13:34:33 -0400
> > 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
> >
> > On Fri, Jun 03, 2005 at 01:21:20PM -0400, John Blackwood wrote:
>
> > >> 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.
I'm not sure of the timeline, but could you check that in a current
2.6.12 GIT snapshot?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-03 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 18:07 [PATCH] ptrace(2) single-stepping into signal handlers John Blackwood
2005-06-03 18:11 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 12:54 John Blackwood
[not found] <d7q7jf$2s8$1@trex.ccur.com>
2005-06-04 13:03 ` John Blackwood
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=20050603181106.GB29940@nevyn.them.org \
--to=dan@debian.org \
--cc=john.blackwood@ccur.com \
--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