public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "nick.alcock at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30026] ctf test program gives weird results with "list"
Date: Thu, 26 Jan 2023 14:05:11 +0000	[thread overview]
Message-ID: <bug-30026-4717-Cx7ufFkmtx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30026-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30026

--- Comment #3 from Nick Alcock <nick.alcock at oracle dot com> ---
Is there any way to say "every source file", "global scope" or failing that
"the source file you're looking at right now"? Picking some random source file
that isn't even the one you're looking at feels hugely confusing and isn't even
right (since any given shared type might not be in scope in that source file at
all, though that's probably not a problem for debugger use, which is one reason
why CTF puts things at global scope so promiscuously.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-01-26 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 18:53 [Bug symtab/30026] New: " tromey at sourceware dot org
2023-01-19 18:56 ` [Bug symtab/30026] " tromey at sourceware dot org
2023-01-23 11:45 ` nick.alcock at oracle dot com
2023-01-23 13:15 ` tromey at sourceware dot org
2023-01-26 14:05 ` nick.alcock at oracle dot com [this message]
2023-01-30  4:16 ` tromey at sourceware dot org
2023-12-06 11:58 ` nick.alcock at oracle dot com
2023-12-06 20:10 ` 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-30026-4717-Cx7ufFkmtx@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: 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).