From: Stephen Smith <ischis2@home.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB <gdb@sources.redhat.com>, Kevin Buettner <kevinb@cygnus.com>,
Michael Elizabeth Chastain <chastain@cygnus.com>
Subject: Re: GDB's remote protocol: My proposed extention
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <3AB90BE2.B3878F54@home.com> (raw)
In-Reply-To: <3AB7867B.3D80F74A@cygnus.com>
> Stephen Smith wrote:
> >
> > When reading chapter 13 of the gdb manual, the rcmd can be taken to mean one
> > of two things:
> >
> > 1) a command sent from the host machine to the target machine for the GDB server/stub to
> > execute
>
> This one. All (well ok almost all) packets are GDB->target->GDB.
>
> Andrew
Ok, I have been poking around in the GDB code like you suggested and here is my proposal for changes in the remote.c
file:
1) Until this is working use an environment variable to turn on this feature * especially since I don't know how to do
it right - yet*
2) Add a "qLibraries" general query. This query would expect a response of the form "sharedLib1, address1;
sharedLib2, address2; sharedLib3, address3"
3) For each library/address pair in the return, call add_symbol_file_command() from symfile.c.
Advantage is that this is a high level function and should be processor/coef/elf independent.
4) Add a "qNewLibraries" general query which would return a `1` or a `0`.
What do you think?
BTW, I keep trying to get a copy of the GNU foundation copyright assignment document so that I can submit the patch when
I am done, haven't
heard a thing from them. Any suggestions on that also?
sps
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 GDB's remote protocol: rCommand Stephen Smith
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Stephen Smith [this message]
2001-03-21 15:59 ` GDB's remote protocol: My proposed extention J.T. Conklin
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 15:59 Stephen Smith
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=3AB90BE2.B3878F54@home.com \
--to=ischis2@home.com \
--cc=ac131313@cygnus.com \
--cc=chastain@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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