public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hi-angel at yandex dot ru" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26644] `info variables` does not show ones defined with #define Date: Wed, 23 Sep 2020 21:32:11 +0000 [thread overview] Message-ID: <bug-26644-4717-PGFRBMdCvi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26644-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26644 --- Comment #2 from Hi-Angel <hi-angel at yandex dot ru> --- (In reply to Tom Tromey from comment #1) > gdb will show this with "info macro". Macros aren't really variables You probably imply that macros can accept arguments, which makes them not to be variables. Well… probably that's fair too. Feel free to close report if you don't think it's actionable. >, and often there are many more in scope than you might think -- enough that > they would overwhelm the output relating to real variables, which is probably > what most users want. I don't think such problem is a thing. If you execute `info variables` with the original testcase which does not even contain includes, you will get so overwhelming amount of output that terminal scrollback won't have enough space. That's why `i variables` supports regexps, to reduce the output. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-09-23 21:32 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-22 10:21 [Bug gdb/26644] New: `info variables` does not show ones defined with macro hi-angel at yandex dot ru 2020-09-22 10:22 ` [Bug gdb/26644] `info variables` does not show ones defined with #define hi-angel at yandex dot ru 2020-09-23 19:51 ` tromey at sourceware dot org 2020-09-23 21:32 ` hi-angel at yandex dot ru [this message] 2020-09-24 12:35 ` tromey at sourceware dot org
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=bug-26644-4717-PGFRBMdCvi@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).