From: "David S. Miller" <davem@redhat.com>
To: ppadala@cise.ufl.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: No PTRACE_READDATA for archs other than SPARC?
Date: Sun, 19 May 2002 21:40:53 -0700 (PDT) [thread overview]
Message-ID: <20020519.214053.19164382.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.05.10205192307500.26915-100000@rain.cise.ufl.edu>
From: Pradeep Padala <ppadala@cise.ufl.edu>
Date: Sun, 19 May 2002 23:08:36 -0400 (EDT)
I was trying to understand ptrace code in kernel. It seems there's
no PTRACE_READDATA for architectures other than sparc and sparc64.
There's a function named ptrace_readdata() in kernel/ptrace.c but I
couldn't find a way to invoke it from user space. Is the feature
missing? or Is it intended?
Only Sparc implements this, that is correct.
If other platforms added PTRACE_READDATA support, they would
also need to add some way to do a feature test for it's presence
so that GDB and other debugging code could actually make use
of it portably.
Another thing I noticed, the prototype for do_ptrace() in
arch/sparc/kernel/ptrace.c is
asmlinkage void do_ptrace(struct pt_regs *regs)
I thought it should be some thing like
asmlinkage int sys_ptrace(long request, long pid, long addr, long
data)
The return values are set directly in the user's pt_regs.
next prev parent reply other threads:[~2002-05-20 4:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 3:08 No PTRACE_READDATA for archs other than SPARC? Pradeep Padala
2002-05-20 4:40 ` David S. Miller [this message]
2002-05-20 6:29 ` Frank Schaefer
2002-05-20 21:18 ` David S. Miller
2002-05-29 23:51 ` Daniel Jacobowitz
2002-05-30 0:03 ` William Lee Irwin III
2002-05-30 0:15 ` Daniel Jacobowitz
2002-05-20 20:12 ` Pradeep Padala
2002-05-29 23:49 ` Daniel Jacobowitz
2002-05-30 0:31 ` David S. Miller
2002-05-30 0:48 ` Daniel Jacobowitz
2002-05-30 15:22 ` Pradeep Padala
2002-06-04 4:37 ` David S. Miller
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=20020519.214053.19164382.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ppadala@cise.ufl.edu \
/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