From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCHv2 3/3] gdb: add "set startup-quietly" command
Date: Tue, 26 Jan 2021 17:12:44 +0200 [thread overview]
Message-ID: <83ft2n20lv.fsf@gnu.org> (raw)
In-Reply-To: <aeee3b64a08b17b9b143d1aaa8bf07b73735ff4a.1611653889.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Tue, 26 Jan 2021 09:48:13 +0000)
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Tue, 26 Jan 2021 09:48:13 +0000
> Cc: Tom Tromey <tom@tromey.com>
>
> From: Tom Tromey <tom@tromey.com>
>
> This adds a new command to change GDB to behave as though "-quiet"
> were always given. This new command can be added to the gdbstartup
> file to affect future GDB sessions.
>
> gdb/ChangeLog:
>
> * NEWS: Add entry.
> * main.c (captured_main_1): Call check_quiet_mode.
> * top.c (startup_quiet): New global.
> (check_quiet_mode): New function.
> (show_startup_quiet): New function.
> (init_main): Register new command.
> * top.h (check_quiet_mode): Declare.
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Mode Options): Mention "set startup-quietly".
>
> gdb/testsuite/ChangeLog:
>
> * gdb.base/startup-file.exp: Add more tests.
Thanks.
> +set startup-quietly on|off
> +show startup-quietly
> + When enabled, this causes GDB to act as if "-silent" were always
> + passed on the command line. This command needs to be added to a
> + gdbstartup file in order to affect GDB.
What is "gdbstartup file"?
Also, the manual seems to describe the use of this feature
differently:
> +@kindex set startup-quietly
> +@kindex show startup-quietly
> +This can also be enabled using @code{set startup-quietly on}. The
> +default is @code{off}. Use @code{show startup-quietly} to see the
> +current setting. Changing this setting will have no affect on the
> +current @value{GDBN} session. Add @code{set startup-quietly on} to
> +the startup command file (@pxref{Initialization Files,,Initialization
> +Files}) to affect future @value{GDBN} sessions.
Why is there a difference between the two descriptions?
Also, the sentence starting with "Changing this setting will have" is
slightly confusing, because it is not absolutely clear that it refers
only to the "set" command issued from the CLI, and does NOT affect the
startup file setting. Could you please clarify this text?
next prev parent reply other threads:[~2021-01-26 15:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 9:48 [PATCHv2 0/3] Adding startup files to GDB Andrew Burgess
2021-01-26 9:48 ` [PATCHv2 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-01-26 15:09 ` Simon Marchi
2021-01-26 9:48 ` [PATCHv2 2/3] gdb: process startup files and startup command line options Andrew Burgess
2021-01-26 15:22 ` Eli Zaretskii
2021-01-26 15:32 ` Simon Marchi
2021-01-26 15:30 ` Simon Marchi
2021-01-26 9:48 ` [PATCHv2 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-01-26 15:12 ` Eli Zaretskii [this message]
2021-02-18 16:41 ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-02-18 16:41 ` [PATCHv3 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-02-18 16:41 ` [PATCHv3 2/3] gdb: process early initialization files and command line options Andrew Burgess
2021-02-18 17:46 ` Eli Zaretskii
2021-03-24 12:10 ` Andrew Burgess
2021-03-24 17:17 ` Eli Zaretskii
2021-02-18 16:41 ` [PATCHv3 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-02-18 17:32 ` Eli Zaretskii
2021-03-24 12:08 ` Andrew Burgess
2021-03-31 20:11 ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-04-02 19:20 ` Tom Tromey
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=83ft2n20lv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).