public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: Document the 'metadata' styling in GDB displays. Date: Mon, 16 May 2022 16:05:54 +0000 (GMT) [thread overview] Message-ID: <20220516160554.5A45B3948833@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8c9b320a8ee438b5db12d5aaa8c0ba08d1b5c29d commit 8c9b320a8ee438b5db12d5aaa8c0ba08d1b5c29d Author: Eli Zaretskii <eliz@gnu.org> Date: Mon May 16 19:03:59 2022 +0300 gdb: Document the 'metadata' styling in GDB displays. The 'metadata' styling was never documented in the GDB manual. This fills that gap. Diff: --- gdb/doc/gdb.texinfo | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 38ad2ac32b0..08d3f703fc9 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -26425,6 +26425,16 @@ the user attention to some specific parts of their output. For example, the command @command{apropos -v REGEXP} uses the highlight style to mark the documentation parts matching @var{regexp}. +@item metadata +Control the styling of data annotations added by @value{GDBN} to data +it displays. By default, this style's intensity is dim. Metadata +annotations include the @samp{repeats @var{n} times} annotation for +suppressed display of repeated array elements (@pxref{Print Strings}), +@samp{<unavailable>} and @w{@samp{<error @var{descr}>}} annotations +for errors and @samp{<optimized-out>} annotations for optimized-out +values in displaying stack frame information in backtraces +(@pxref{Backtrace}), etc. + @item tui-border Control the styling of the TUI border. Note that, unlike other styling options, only the color of the border can be controlled via
reply other threads:[~2022-05-16 16:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220516160554.5A45B3948833@sourceware.org \ --to=eliz@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).