From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA, doc RFA] Add "set debug symfile on".
Date: Wed, 25 Sep 2013 05:57:00 -0000 [thread overview]
Message-ID: <83k3i5h28j.fsf@gnu.org> (raw)
In-Reply-To: <yjt261tpbvdj.fsf@ruffy.mtv.corp.google.com>
> From: Doug Evans <dje@google.com>
> Date: Tue, 24 Sep 2013 17:25:12 -0700
>
> Hi.
>
> This patch adds a new debugging option: set debug symfile on
>
> For now it logs all calls through the symfile functions.
>
> Regression tested on amd64-linux.
>
> Ok to check in?
Thanks.
> --- NEWS 16 Sep 2013 17:47:29 -0000 1.614
> +++ NEWS 25 Sep 2013 00:03:11 -0000
> @@ -46,6 +46,10 @@ maint set|show per-command symtab
>
> * New options
>
> +set debug symfile off|on
> +show debug symfile
> + Control display of debugging info for symfile functions.
I'm not sure everybody knows what a "symfile" is. How about this
instead:
Control display of debugging info regarding reading symbol files and
symbol tables within those files.
> --- doc/gdb.texinfo 16 Sep 2013 18:00:34 -0000 1.1112
> +++ doc/gdb.texinfo 25 Sep 2013 00:03:12 -0000
> @@ -22573,6 +22573,12 @@ Turns on or off debugging messages for F
> @item show debug solib-frv
> Display the current state of FR-V shared-library code debugging
> messages.
> +@item set debug symfile
> +@cindex symbol file functions
> +Turns on or off display of debugging messages related to symbol file functions.
This could use a cross-reference to where symbol files are described
(the "Files" node).
> +The default is off.
> +@item show debug symfile
> +Show the current state of symbol file debugging.
"Show the current state of symbol file debugging messages."
OK with those changes.
next prev parent reply other threads:[~2013-09-25 5:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 0:25 Doug Evans
2013-09-25 0:31 ` Doug Evans
2013-09-25 5:57 ` Eli Zaretskii [this message]
2013-09-25 19:57 ` Tom Tromey
2013-09-25 21:03 ` Doug Evans
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=83k3i5h28j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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