Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: Jonathan Larmour <jlarmour@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Remote protocol symbol lookup service.
Date: Wed, 06 Jun 2001 03:23:00 -0000	[thread overview]
Message-ID: <3B1E04D2.6090207@cygnus.com> (raw)
In-Reply-To: <3AF199A3.886F469E@cygnus.com>

> Hmmm...  I suppose so, under the right set of assumptions.
> Such as that the target is not really stopped, and we do not
> need to restart it (as with the 'O' packet).
> 
> Andrew?  J.T.?  Anybody else have an opinion about letting GDB
> respond to new requests while in remote_wait?  Basically it's a
> switch statement, so it doesn't really have much impact on 
> performance or anything...  and of course I could abstract the
> code that responds to the symbol requests into a function.
> 
> Or, we could just wait and do this if there's ever a need to.
> For my application (the thread_db interface), this would not
> be useful.


See previous discussion about getting input working across the protocol. 
  The suggestion was:

	o	target stop with bogus signal 0

	o	gdb chat to target: qSymbol? qInput?

	o	gdb resume target

part of the chat could include a check qSymbol check.  A variation might 
have the target return a symbol request instead of a stop status.

	Andrew



  parent reply	other threads:[~2001-06-06  3:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 15:15 Michael Snyder
2001-05-02 15:56 ` Michael Snyder
2001-05-03  4:27   ` Jonathan Larmour
2001-05-03 10:09     ` Michael Snyder
2001-05-03 10:24       ` Jonathan Larmour
2001-05-03 10:47         ` Michael Snyder
2001-05-03 11:15           ` Jonathan Larmour
2001-06-06  3:23           ` Andrew Cagney [this message]
2001-05-10  8:33   ` Andrew Cagney
2001-05-10 18:54     ` Michael Snyder
2001-05-11 18:28       ` Andrew Cagney
2001-05-11 18:39         ` Michael Snyder

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=3B1E04D2.6090207@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=msnyder@cygnus.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