From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] set print symbol-loading on|off
Date: Sat, 19 Jul 2008 22:38:00 -0000 [thread overview]
Message-ID: <E1KKL3g-0005bZ-OB@fencepost.gnu.org> (raw)
In-Reply-To: <20080710203701.6AF041C769A@localhost> (dje@google.com)
> Date: Thu, 10 Jul 2008 13:37:01 -0700 (PDT)
> From: dje@google.com (Doug Evans)
>
> Along the lines of "set print thread-events on|off",
> this option lets one turn off symbol loading messages.
> If the app has *lots* of shared libraries, these messages
> can be more noise than signal.
Thanks.
> --- NEWS 10 Jul 2008 16:44:47 -0000 1.280
> +++ NEWS 10 Jul 2008 20:16:31 -0000
> @@ -68,6 +68,10 @@ find [/size-char] [/max-count] start-add
> val1 [, val2, ...]
> Search memory for a sequence of bytes.
>
> +set print symbol-loading
> +show print symbol-loading
> + Control printing of symbol loading messages.
This is okay.
> - printf_unfiltered (_("Reading symbols from %s..."), name);
> - wrap_here ("");
> - gdb_flush (gdb_stdout);
> + if (print_symbol_loading)
> + {
> + printf_unfiltered (_("Reading symbols from %s..."), name);
> + wrap_here ("");
> + gdb_flush (gdb_stdout);
> + }
I'm not sure doing this in complete silence is a good idea. You've
shut up GDB, but this phase could take a long time, during which GDB
will appear to be hung. How about printing a single message, like
"Reading symbols ..."?
> + add_setshow_boolean_cmd ("symbol-loading", no_class,
> + &print_symbol_loading, _("\
> +Set printing of symbol loading messages."), _("\
> +Show printing of symbol loading messages."), NULL,
This is not enough detail. As written, this doc string doesn't really
document anything in a useful manner. Please add an explanation of
what this does, e.g. "When ON (the default), GDB will print messages
about loading symbols from shared libraries and debug info files."
> Index: doc/gdb.texinfo
> ===================================================================
> RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
This part is okay. Thanks.
next prev parent reply other threads:[~2008-07-19 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 20:37 Doug Evans
2008-07-10 21:42 ` Stan Shebs
2008-07-19 22:38 ` Eli Zaretskii [this message]
2008-07-23 22:47 ` Doug Evans
[not found] ` <e394668d0807231541lf56cd50pdffbef18d0896735@mail.gmail.com>
2008-07-24 11:21 ` Eli Zaretskii
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=E1KKL3g-0005bZ-OB@fencepost.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