From: Eli Zaretskii <eliz@gnu.org>
To: lgustavo@codesourcery.com
Cc: nicolas.blanc@intel.com, gdb-patches@sourceware.org,
palves@redhat.com, tromey@redhat.com, yao@codesourcery.com,
dje@google.com
Subject: Re: [patch v6 3/3] Documentation for the remove-symbol-file command.
Date: Thu, 06 Jun 2013 16:17:00 -0000 [thread overview]
Message-ID: <83r4gfusbv.fsf@gnu.org> (raw)
In-Reply-To: <51B0AF88.7090909@codesourcery.com>
> Date: Thu, 06 Jun 2013 17:49:28 +0200
> From: Luis Machado <lgustavo@codesourcery.com>
> CC: gdb-patches@sourceware.org, palves@redhat.com, tromey@redhat.com,
> eliz@gnu.org, yao@codesourcery.com, dje@google.com
>
> > +remove-symbol-file FILENAME
> > +remove-symbol-file -a ADDRESS
> > + Remove a symbol file added via add-symbol-file. The file to remove
> > + can be identified by its filename or by an address pointing inside
> > + one of its sections.
> > +
>
> I'd rewrite this one to read a little better. Eli may have a better
> suggestion.
>
> Something like this?
>
> Remove a symbol file added via add-symbol-file. The symbol file to
> remove can be identified by its filename or by an address that lies
> within the boundaries of this symbol file in memory.
These two variants seem to have different semantics.
> > +@kindex remove-symbol-file
> > +@item remove-symbol-file @var{filename}
> > +@item remove-symbol-file -a @var{address}
> > +Remove a symbol file added via the @code{add-symbol-file} command. The
> > +file to remove can be identified by its filename or by an address pointing
> > +inside one of its sections. Example:
>
> Same as above?
"filename" and "address" should be in @var.
next prev parent reply other threads:[~2013-06-06 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 19:08 [patch v6 0/3] remove-symbol-file Nicolas Blanc
2013-06-05 19:08 ` [patch v6 2/3] Test adding and removing a symbol file at runtime Nicolas Blanc
2013-06-06 15:47 ` Luis Machado
2013-06-05 19:08 ` [patch v6 3/3] Documentation for the remove-symbol-file command Nicolas Blanc
2013-06-06 15:49 ` Luis Machado
2013-06-06 16:17 ` Eli Zaretskii [this message]
2013-06-05 19:08 ` [patch v6 1/3] New " Nicolas Blanc
2013-06-06 15:44 ` Luis Machado
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=83r4gfusbv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=nicolas.blanc@intel.com \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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