From: Daniel Jacobowitz <dan@debian.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Fabiano Ramos <ramos_fabiano@yahoo.com.br>,
Andi Kleen <ak@muc.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ptrace in 2.6.5
Date: Mon, 10 May 2004 18:58:19 -0400 [thread overview]
Message-ID: <20040510225818.GA24796@nevyn.them.org> (raw)
In-Reply-To: <873c67yk5v.fsf@devron.myhome.or.jp>
On Tue, May 11, 2004 at 07:47:08AM +0900, OGAWA Hirofumi wrote:
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
>
> > So single-step exception happen *after* executed the "mov ...".
> > Probably you need to use the breakpoint instead of single-step.
>
> Ah, sorry. Just use PTRACE_SYSCALL instead of PTRACE_SINGLESTEP.
> It's will stop before/after does syscall.
Doing it this way is pretty lousy - you have to inspect the code after
every step to see if it's an int $0x80. Is there some reason not to
report a trap on the syscall return path if single-stepping?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-10 23:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1UlcA-6lq-9@gated-at.bofh.it>
2004-05-10 18:49 ` ptrace in 2.6.5 Andi Kleen
2004-05-10 19:37 ` Davide Libenzi
2004-05-10 20:24 ` Fabiano Ramos
2004-05-10 21:49 ` OGAWA Hirofumi
2004-05-10 22:47 ` OGAWA Hirofumi
2004-05-10 22:58 ` Daniel Jacobowitz [this message]
2004-05-10 23:12 ` Davide Libenzi
2004-05-11 0:40 ` Fabiano Ramos
2004-05-11 6:14 ` Davide Libenzi
2004-05-11 6:27 ` Davide Libenzi
2004-05-11 6:41 ` Davide Libenzi
2004-05-11 14:07 ` Daniel Jacobowitz
2004-05-10 15:46 Fabiano Ramos
2004-05-10 16:10 ` Daniel Jacobowitz
2004-05-10 16:22 ` Fabiano Ramos
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=20040510225818.GA24796@nevyn.them.org \
--to=dan@debian.org \
--cc=ak@muc.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=ramos_fabiano@yahoo.com.br \
/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.