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/29398] [gdb/symtab] lazy CU expansion
Date: Sun, 24 Jul 2022 08:36:51 +0000 [thread overview]
Message-ID: <bug-29398-4717-Hq0dBHhPpi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29398-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29398
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> Also I think it would require fixing the .debug_names
> bug,
Can you point out which one? Is it perhaps PR24820?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-24 8:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 8:25 [Bug symtab/29398] New: " vries at gcc dot gnu.org
2022-07-24 8:36 ` vries at gcc dot gnu.org [this message]
2022-07-24 8:43 ` [Bug symtab/29398] " vries at gcc dot gnu.org
2022-07-24 8:46 ` vries at gcc dot gnu.org
2022-10-21 17:20 ` tromey at sourceware dot org
2022-12-21 19:55 ` tromey at sourceware dot org
2022-12-25 20:03 ` tromey at sourceware dot org
2023-04-03 14:58 ` tromey at sourceware dot org
2023-10-25 8:44 ` sam at gentoo dot org
2023-11-25 18:12 ` tromey at sourceware dot org
2024-01-21 22:17 ` tromey at sourceware dot org
2024-01-23 0:24 ` tromey at sourceware dot org
2024-02-09 20:15 ` 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-29398-4717-Hq0dBHhPpi@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).