From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA PATCH] Accept "set foo unlimited" in integer/uinteger/zuinteger_unlimited commands.
Date: Wed, 27 Mar 2013 18:51:00 -0000 [thread overview]
Message-ID: <838v58ybic.fsf@gnu.org> (raw)
In-Reply-To: <20130327164510.30832.43521.stgit@brno.lan>
> From: Pedro Alves <palves@redhat.com>
> Date: Wed, 27 Mar 2013 16:45:10 +0000
>
> Currently, several commands take "0" or "-1" to mean "unlimited".
>
> "show" knows when to print "unlimited":
>
> (gdb) show height
> Number of lines gdb thinks are in a page is 45.
> (gdb) set height 0
> (gdb) show height
> Number of lines gdb thinks are in a page is unlimited.
>
> However, the user can't herself specify "unlimited" directly:
>
> (gdb) set height unlimited
> No symbol table is loaded. Use the "file" command.
> (gdb)
>
> This patch addresses that, by adjusting the set handler for all
> integer/uinteger/zuinteger_unlimited commands to accept literal
> "unlimited". It also installs a completer.
Thanks!
> Okay?
A few comments from me:
> gdb/doc/
> 2013-03-27 Pedro Alves <palves@redhat.com>
>
> * gdb.texinfo (set record full insn-number-max): Document
> "unlimited".
> (set record instruction-history-size): Likewise.
> (set record function-call-history-size): Likewise.
> (set backtrace limit): Likewise.
> (set listsize): Likewise.
> (set print max-symbolic-offset): Likewise.
> (set print elements): Likewise.
> (set print repeats): Likewise.
> (set trace-buffer-size): Likewise.
> (set tcp connect-timeout): Likewise.
> (set history size): Likewise.
> (set height):
> (set width):
> (set pagination): Adjust to suggest "set height unlimited" instead
> of "set height 0".
Those aren't node names in the parens. I thought we were always using
node names there.
> +If @var{limit} is @code{unlimited}, or zero, @value{GDBN} will never
^
This comma should be deleted.
> + The number of
> +recorded instructions is unlimited in this case.
^^^^^^^^^^^^
I'd say "... is limited only by the available memory" instead.
The documentation parts are OK with those changes.
next prev parent reply other threads:[~2013-03-27 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 18:22 Pedro Alves
2013-03-27 18:51 ` Eli Zaretskii [this message]
2013-03-27 20:44 ` Pedro Alves
2013-04-10 22:55 ` Pedro Alves
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=838v58ybic.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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