Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, Daniel Jacobowitz <drow@mvista.com>
Cc: wim delvaux <wim.delvaux@adaptiveplanet.com>, gdb@sources.redhat.com
Subject: Re: why is gdb 5.2 so slow
Date: Fri, 01 Nov 2002 10:44:00 -0000	[thread overview]
Message-ID: <1021101184351.ZM22820@localhost.localdomain> (raw)
In-Reply-To: Andrew Cagney <ac131313@redhat.com> "Re: why is gdb 5.2 so slow" (Nov  1,  1:32pm)

On Nov 1,  1:32pm, Andrew Cagney wrote:

> > In any case, this reminded me of something I keep forgetting.  Modern
> > kernels a ptrace-attached process can open the child's /proc/<pid>/mem
> > and read from it.  Writing to it is disabled, and mmap is not
> > implemented (oh the violence to the mm layer if that was allowed!). 
> > But reading from it is probably faster than PTRACE_PEEKTEXT.  I'll
> > investigate.
> 
> Ah.  How does solaris work then?

On Solaris, /proc provides a complete debug interface.  On Linux, it doesn't.

Kevin


  reply	other threads:[~2002-11-01 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 17:32 wim delvaux
2002-10-31 19:51 ` Daniel Jacobowitz
2002-11-01  5:31   ` wim delvaux
2002-11-01  6:58     ` Andrew Cagney
2002-11-01  7:15       ` wim delvaux
2002-11-01  7:17         ` Daniel Jacobowitz
2002-11-01  8:13           ` wim delvaux
2002-11-01  7:15       ` Daniel Jacobowitz
2002-11-01  8:55         ` Andrew Cagney
2002-11-01 10:14           ` Daniel Jacobowitz
2002-11-01 10:32             ` Andrew Cagney
2002-11-01 10:44               ` Kevin Buettner [this message]
     [not found]       ` <redirect-4290038@silicondust.com>
2002-11-01  8:36         ` Nick Kelsey
2002-11-01 11:43 Howell, David P
2002-11-01 12:46 ` Andrew Cagney
2002-11-04 12:44   ` Jim Blandy

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=1021101184351.ZM22820@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=wim.delvaux@adaptiveplanet.com \
    /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