From: Andi Kleen <ak@suse.de>
To: Roland McGrath <roland@redhat.com>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64: ptrace ia32 BP fix
Date: Tue, 5 Jul 2005 16:16:51 +0200 [thread overview]
Message-ID: <20050705141651.GW21330@wotan.suse.de> (raw)
In-Reply-To: <20050705140724.GA19552@nevyn.them.org>
> Wouldn't this to botch a debugger which supported both backtracing and
> PTRACE_SYSCALL, when stopped in a syscall? We have unwind information
> for the VDSO and it's not going to tell us that the kernel has done
> something clever to the value of %ebp.
The kernel is indeed not supposed to modify any input
registers of syscalls (ok except rcx, but that is unavoidable)
-Andi
next prev parent reply other threads:[~2005-07-05 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 9:31 Roland McGrath
2005-07-05 14:07 ` Daniel Jacobowitz
2005-07-05 14:16 ` Andi Kleen [this message]
2005-07-05 19:11 ` Roland McGrath
[not found] <20050705095916.GV21330@wotan.suse.de>
2005-07-05 10:19 ` Roland McGrath
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=20050705141651.GW21330@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®