Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Use PT_IO ptrace request if available
Date: Fri, 08 Nov 2002 16:08:00 -0000	[thread overview]
Message-ID: <20021109000931.GA20735@nevyn.them.org> (raw)
In-Reply-To: <200211082358.gA8Nw2Dj017053@elgar.kettenis.dyndns.org>

On Sat, Nov 09, 2002 at 12:58:02AM +0100, Mark Kettenis wrote:
> The attached patch makes use of the PT_IO ptrace request that's
> available in *BSD for data transfers to/from the inferior.  It's a
> couple of weeks ago now that my patch that fixes the FreeBSD
> 5.0-CURRENT kernel went in, and I hope that OpenBSD and NetBSD don't
> have any problems.  We'll probably find out soon :-).  Note that if
> you run FreeBSD 5.0-CURRENT from before October 16 and after March 16,
> your machine will probably lock up when using GDB.  However, since
> -CURRENT is a development version, I think it's acceptable to ask
> people to upgrade.
> 
> It would be great if we could get Linux to support the same interface.

We've got read covered, from /proc/<pid>/mem; I'm going to implement
that when I get a chance.

I suppose I could implement PT_IO the way you did... I was planning on
a Sun-style PTRACE_READDATA (SPARC Linux already has this) but it's not
possible on i386 (syscall with five arguments).  I'm not sure it's
worth it; it's generally reading that we do in bulk, not writing.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-11-09  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08 15:58 Mark Kettenis
2002-11-08 16:08 ` Daniel Jacobowitz [this message]

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=20021109000931.GA20735@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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