From: Fabiano Ramos <ramos_fabiano@yahoo.com.br>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Davide Libenzi <davidel@xmailserver.org>
Subject: Re: [patch] really-ptrace-single-step
Date: Tue, 11 May 2004 14:36:54 -0300 [thread overview]
Message-ID: <1084297014.1729.10.camel@slack.domain.invalid> (raw)
In-Reply-To: <Pine.LNX.4.58.0405111007440.25232@bigblue.dev.mdolabs.com>
It would not work against 2.6.5, since
do_syscall_trace()
makes the check
if (!test_thread_flag(TIF_SYSCALL_TRACE))
return;
Simply removing it would do?
On Tue, 2004-05-11 at 14:12, Davide Libenzi wrote:
> This patch lets a ptrace process on x86 to "see" the instruction
> following the INT #80h op.
>
>
>
> - Davide
>
>
> arch/i386/kernel/entry.S | 2 +-
> include/asm-i386/thread_info.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>
>
>
> Index: arch/i386/kernel/entry.S
> ===================================================================
> RCS file: /usr/src/bkcvs/linux-2.5/arch/i386/kernel/entry.S,v
> retrieving revision 1.83
> diff -u -r1.83 entry.S
> --- arch/i386/kernel/entry.S 12 Apr 2004 20:29:12 -0000 1.83
> +++ arch/i386/kernel/entry.S 11 May 2004 06:35:29 -0000
> @@ -354,7 +354,7 @@
> # perform syscall exit tracing
> ALIGN
> syscall_exit_work:
> - testb $(_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT), %cl
> + testb $(_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT|_TIF_SINGLESTEP), %cl
> jz work_pending
> sti # could let do_syscall_trace() call
> # schedule() instead
> Index: include/asm-i386/thread_info.h
> ===================================================================
> RCS file: /usr/src/bkcvs/linux-2.5/include/asm-i386/thread_info.h,v
> retrieving revision 1.19
> diff -u -r1.19 thread_info.h
> --- include/asm-i386/thread_info.h 12 Apr 2004 20:29:12 -0000 1.19
> +++ include/asm-i386/thread_info.h 11 May 2004 06:34:47 -0000
> @@ -165,7 +165,7 @@
>
> /* work to do on interrupt/exception return */
> #define _TIF_WORK_MASK \
> - (0x0000FFFF & ~(_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT))
> + (0x0000FFFF & ~(_TIF_SYSCALL_TRACE|_TIF_SYSCALL_AUDIT|_TIF_SINGLESTEP))
> #define _TIF_ALLWORK_MASK 0x0000FFFF /* work to do on any return to u-space */
>
> /*
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-05-11 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 17:12 [patch] really-ptrace-single-step Davide Libenzi
2004-05-11 17:31 ` Fabiano Ramos
2004-05-12 0:17 ` Andrew Morton
2004-05-12 0:42 ` Davide Libenzi
2004-05-12 1:04 ` Fabiano Ramos
2004-05-12 1:06 ` Davide Libenzi
2004-05-12 1:15 ` Fabiano Ramos
2004-05-12 2:19 ` Fabiano Ramos
2004-05-11 17:36 ` Fabiano Ramos [this message]
2004-05-11 17:38 ` Davide Libenzi
2004-05-11 18:40 ` 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=1084297014.1729.10.camel@slack.domain.invalid \
--to=ramos_fabiano@yahoo.com.br \
--cc=davidel@xmailserver.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