public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: Metadata style?
Date: Thu, 07 Apr 2022 12:44:42 -0600	[thread overview]
Message-ID: <87sfqo91id.fsf@tromey.com> (raw)
In-Reply-To: <83tubh9aqc.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 28 Mar 2022 21:46:03 +0300")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Eli> The command "show style" includes this part:
Eli>   style metadata background:  The "metadata" style background color is: none
Eli>   style metadata foreground:  The "metadata" style foreground color is: none
Eli>   style metadata intensity:  The "metadata" style display intensity is: dim

Eli> But there's no explanation in the manual what is the "metadata"
Eli> object.  What is it, and how can I display it in GDB to see the style
Eli> in action?

First, sorry about this, I completely slipped on writing documentation
for this.

There's a test for this style:

	gdb_test_no_output "set print repeat 3"
	gdb_test "print {0,0,0,0,0,0,0,0}" \
	    " = \\{0 [limited_style {<repeats.*8.*times>} metadata]\\}"

It's used in a number of places where gdb is attempting to display some
kind of data from the inferior but instead prints some
internally-generated text, e.g.:

  fprintf_styled (stream, metadata_style.style (), _("<unavailable>"));

I'm not completely sure of the best way to describe this.

Tom

  parent reply	other threads:[~2022-04-07 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 18:46 Eli Zaretskii
2022-04-07 11:14 ` Eli Zaretskii
2022-04-07 18:44 ` Tom Tromey [this message]
2022-04-10  8:55   ` Eli Zaretskii
2022-04-26 12:02     ` Eli Zaretskii
2022-05-04 12:40       ` Eli Zaretskii
2022-05-16 14:11     ` Tom Tromey
2022-05-16 16:06       ` 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=87sfqo91id.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=eliz@gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).