From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: gdb@sources.redhat.com
Subject: Re: more on gdb server
Date: Wed, 18 Jul 2001 09:41:00 -0000 [thread overview]
Message-ID: <20010718094143.A24443@nevyn.them.org> (raw)
In-Reply-To: <200107181323.f6IDNtw14885@scv2.apple.com>
On Tue, Jul 17, 2001 at 05:25:08PM -0700, Stan Shebs wrote:
> On Tuesday, July 17, 2001, at 11:57 AM, Quality Quorum wrote:
>
> > Hi,
> >
> > I am not sure I am right about it, but it seems quite a neat idea to use
> > gdbserver as a primary interface even for a local debugging. It is cheap
> > resource wise and will provide for a neat separation of debugger per se
> > and (target dependable) target control code.
>
> I'm not convinced that the overhead is negligible. You're
> inserting an additional program and network stack trip in one
> of the two known time-critical parts of GDB. I think it should
> be *possible* to use gdbserver all the time, but I'd want to see
> encouraging performance numbers before advocating that we commit
> to using it. (Having gdbserver functional on all native configs
> is kind of a prerequisite too. :-) )
I'd be more interested in making it possible to run the testsuite using
a native gdbserver; unless someone else does (or is it already possible
and just not well-documented?) I'll look in to this.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-18 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[not found] <3B55A2E7.9040304@cygnus.com>
2001-07-18 9:34 ` Quality Quorum
[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
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=20010718094143.A24443@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=gdb@sources.redhat.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