public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30863] [gdb/symtab] PU without import read by readnow
Date: Thu, 05 Mar 2026 10:44:57 +0000 [thread overview]
Message-ID: <bug-30863-4717-rr8sbwCIg9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30863-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30863
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
Summary|[gdb/symtab] PU without |[gdb/symtab] PU without
|import ignored in cooked |import read by readnow
|index |
Target Milestone|--- |18.1
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #6)
> Since searching is now done via the index, non-imported PUs
> should probably be ignored already even with -readnow.
>
The main thing I was concerned with was consistency between using and not using
-readnow, and AFAIU we have that now. So I consider this fixed. Updating
$subject to reflect this.
> In any case, I don't think this is really a bug. A non-imported PU
> is a bug in the DWARF writer.
Agreed.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2026-03-05 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 7:13 [Bug symtab/30863] New: [gdb/symtab] PU without import ignored in cooked index vries at gcc dot gnu.org
2023-09-17 7:16 ` [Bug symtab/30863] " vries at gcc dot gnu.org
2023-09-17 8:53 ` vries at gcc dot gnu.org
2023-09-17 9:57 ` vries at gcc dot gnu.org
2023-09-17 12:27 ` tromey at sourceware dot org
2023-11-30 17:07 ` tromey at sourceware dot org
2025-11-26 16:38 ` tromey at sourceware dot org
2026-01-24 21:20 ` tromey at sourceware dot org
2026-03-04 14:31 ` tromey at sourceware dot org
2026-03-05 10:44 ` vries at gcc dot gnu.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-30863-4717-rr8sbwCIg9@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).