From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: [remote protocol] Allow qSymbol response to continue packets
Date: Sat, 06 Mar 2004 23:52:00 -0000 [thread overview]
Message-ID: <20040306235253.GA10376@nevyn.them.org> (raw)
I'd like to propose the attached as an extension to the remote protocol.
The code implementing this change is here:
http://sources.redhat.com/ml/gdb-patches/2004-02/msg00000.html
From my original post:
As Amit Kale mentioned in December, to support NPTL gdbserver needs to
look up symbols during remote_wait. The existing qSymbol model assumes
that only at objfile loads (i.e. during td_ta_new) do we need to look up
symbols; NPTL looks up symbols lazily when it needs them, which includes
at the creation of the first child thread. This patch (which, I know,
needs a matching change for the manual) allows qSymbol: queries as a
response to remote_wait, in much the same way as the file I/O protocol.
So here's the manual page and a description of the change. Thoughts?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2004-03-06 Daniel Jacobowitz <drow@mvista.com>
* gdb.texinfo (Stop Reply Packets): Define qSymbol response.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.199
diff -u -p -r1.199 gdb.texinfo
--- gdb.texinfo 29 Feb 2004 02:57:24 -0000 1.199
+++ gdb.texinfo 6 Mar 2004 23:48:15 -0000
@@ -20267,6 +20267,15 @@ packet from the target. The latest @sam
@samp{s} action is expected to be continued.
@xref{File-I/O remote protocol extension}, for more details.
+@item qSymbol:@var{sym_name}
+
+The target is requesting the address of a symbol. @value{GDBN} replies with
+a @code{qSymbol} packet providing the address of @var{sym_name} if available
+(@pxref{General Query Packets}).
+
+As with @code{F}, this response does not terminate the current resume
+action. @value{GDBN} continues waiting for another stop packet.
+
@end table
@node General Query Packets
next reply other threads:[~2004-03-06 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 23:52 Daniel Jacobowitz [this message]
2004-03-07 5:45 ` Eli Zaretskii
2004-03-11 20:06 ` Andrew Cagney
2004-03-11 20:16 ` Daniel Jacobowitz
2004-03-11 21:27 ` Andrew Cagney
2004-03-11 21:40 ` Daniel Jacobowitz
2004-03-11 23:21 ` Andrew Cagney
2004-03-11 23:38 ` Daniel Jacobowitz
2004-03-12 19:45 ` Daniel Jacobowitz
2004-03-17 16:07 ` 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=20040306235253.GA10376@nevyn.them.org \
--to=drow@false.org \
--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