From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: msnyder@cygnus.com
Cc: gdb-patches@sources.redhat.com, cagney@cygnus.com
Subject: Re: [RFA] Remote symbol look-up (resubmission)
Date: Fri, 11 May 2001 12:39:00 -0000 [thread overview]
Message-ID: <9427-Fri11May2001223943+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3AFC20A5.700ACFAF@cygnus.com>
> Date: Fri, 11 May 2001 10:25:57 -0700
> From: Michael Snyder <msnyder@cygnus.com>
>
> This is a re-submission, with documentation and changes to answer Andrew's concerns.
>
>
> 2001-05-10 Michael Snyder <msnyder@redhat.com>
>
> * solib.h (no_shared_libraries): Export definition.
> * remote.c (remote_new_objfile): New function. Called whenever
> a new objfile is created (which is generally a new shared library).
> (remote_check_symbols): Send notification to the target that it is
> now a good time to ask for symbol look-up service, and handle any
> symbol look-up requests. Called whenever a new symbol file becomes
> available, and from remote open.
> (hex2bin): Require explicit count, don't accept null-terminated str.
> (set_remote_protocol_qSymbol_packet_cmd): New function.
> (show_remote_protocol_qSymbol_packet_cmd): New function.
> (remote_open_1, remote_async_open_1): Call remote_check_symbols.
> (_initialize_remote): Hook remote_new_objfile into the new
> objfile notification chain. Add set/show remote symbol-lookup
> commands.
> * doc/gdb.texinfo: Document the new 'qSymbol' and 'QSymbol' packets.
The changes to gdb.texinfo are approved, but please correct one minor
problem:
> + @tab @code{q}@code{Symbol:}@var{SYMBOL_FILE_NAME}
Please write the arguments of @var{} in lower case. They will be
converted to upper case by makeinfo, but in the printed manual @var is
typeset with a special font which makes it stand out without upcasing
the text. (There are several other places which use @var{FOO}.)
next prev parent reply other threads:[~2001-05-11 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 10:26 Michael Snyder
2001-05-11 12:39 ` Eli Zaretskii [this message]
2001-05-11 18:51 ` Michael Snyder
2001-05-11 19:57 ` Andrew Cagney
2001-05-14 11:18 ` Michael Snyder
2001-05-14 13:37 ` Andrew Cagney
2001-05-14 14:34 ` Michael Snyder
2001-05-17 20:44 ` Andrew Cagney
2001-05-21 15:12 ` Michael Snyder
2001-05-21 15:30 ` Michael Snyder
2001-06-06 9: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=9427-Fri11May2001223943+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=cagney@cygnus.com \
--cc=gdb-patches@sources.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