From: Quality Quorum <qqi@world.std.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Stan Shebs <shebs@apple.com>, gdb@sources.redhat.com
Subject: Re: more on gdb server
Date: Wed, 18 Jul 2001 09:34:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.21.0107181232060.13093-100000@world.std.com> (raw)
In-Reply-To: <3B55A2E7.9040304@cygnus.com>
> I know HP were once playing with ideas that would have eliminated any
> copying because they were finding memory read/write performance using
> ptrace (or what ever) lacking.
I would suppose they had something truly unusual - debuggin is going with
the pace of human reaction to debugging events and I can hardly imagine
that network performance over local loop interface would be a factor here.
>
> enjoy,
> Andrew
Thanks,
Aleksey
next parent reply other threads:[~2001-07-18 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B55A2E7.9040304@cygnus.com>
2001-07-18 9:34 ` Quality Quorum [this message]
[not found] <5mitgq6ug4.fsf@orac.redback.com>
2001-07-18 12:41 ` Quality Quorum
2001-07-18 12:49 ` Daniel Jacobowitz
2001-07-18 13:53 ` Quality Quorum
2001-07-18 14:05 ` Andrew Cagney
2001-07-17 11:57 Quality Quorum
2001-07-18 6:24 ` Stan Shebs
2001-07-18 6:52 ` Quality Quorum
2001-07-18 9:41 ` Daniel Jacobowitz
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=Pine.SGI.4.21.0107181232060.13093-100000@world.std.com \
--to=qqi@world.std.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=shebs@apple.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