public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30946] [gdb/symtab, gdb-index] FAIL: gdb.fortran/nested-funcs-2.exp: src_prefix=0: nest_prefix=1: before start: info symbol contains_keyword::increment Date: Sun, 10 Dec 2023 16:15:45 +0000 [thread overview] Message-ID: <bug-30946-4717-q1ckl3zVbW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30946-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30946 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #2 from Tom Tromey <tromey at sourceware dot org> --- FWIW this test works fine with my .debug_names rewrite, even with the demonstrator patch applied. And 'maint info symtabs' shows that nothing is pre-expanded. For me this is a bit mysterious in that I'd expect the results to be similar for .gdb_index. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-10 16:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-06 13:07 [Bug symtab/30946] New: " vries at gcc dot gnu.org 2023-10-10 8:26 ` [Bug symtab/30946] " cvs-commit at gcc dot gnu.org 2023-12-10 16:15 ` tromey at sourceware dot org [this message]
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-30946-4717-q1ckl3zVbW@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).