From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: "David S. Miller" <davem@redhat.com>
Cc: ppadala@cise.ufl.edu, linux-kernel@vger.kernel.org
Subject: Re: No PTRACE_READDATA for archs other than SPARC?
Date: Wed, 29 May 2002 20:48:12 -0400 [thread overview]
Message-ID: <20020530004811.GA5921@branoic.them.org> (raw)
In-Reply-To: <Pine.GSO.4.05.10205192307500.26915-100000@rain.cise.ufl.edu> <20020519.214053.19164382.davem@redhat.com> <20020529234951.GA3797@branoic.them.org> <20020529.173118.130757558.davem@redhat.com>
On Wed, May 29, 2002 at 05:31:18PM -0700, David S. Miller wrote:
> From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
> Date: Wed, 29 May 2002 19:49:51 -0400
>
> On Sun, May 19, 2002 at 09:40:53PM -0700, David S. Miller wrote:
> > 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.
>
> Not really, we should just get EINVAL (ENOSYS?) back when we try to use
> it, right?
>
> You'd get -EIO, but otherwise yes you are right.
Really? That's inconvenient; the same result as for an invalid memory
address.
Oh well, it can still be worked around in GDB. I'd like to see this on
more/all architectures.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-30 0:48 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
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 [this message]
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=20020530004811.GA5921@branoic.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=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