public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "josh.cottingham at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/31010] Evaluating "mixed-cased" fundamental types causes hangs/OOM due to full symtab expansion
Date: Tue, 04 Feb 2025 15:38:45 +0000 [thread overview]
Message-ID: <bug-31010-4717-y6cs1fFA3M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31010-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31010
Josh Cottingham <josh.cottingham at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DUPLICATE |---
Status|RESOLVED |UNCONFIRMED
--- Comment #3 from Josh Cottingham <josh.cottingham at linaro dot org> ---
After trying with both GDB 15.1 and GDB 16.1 I am lead to believe that this
issue has not actually been solved in bug 30520.
When testing with the following patch
https://sourceware.org/pipermail/gdb-patches/2024-January/205924.html it did
appear to be solved and no longer occurring.
However, since then it looks like it was proposed to move to from name matching
the full name to name matching on the canonical name. By the time the patch was
implemented again with this change in
https://sourceware.org/pipermail/gdb-patches/2024-May/209010.html it appears
that this issue was still occurring.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2025-02-04 15:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:38 [Bug symtab/31010] New: " josh.cottingham at linaro dot org
2023-10-30 16:40 ` [Bug symtab/31010] " josh.cottingham at linaro dot org
2023-10-31 4:14 ` sam at gentoo dot org
2023-10-31 17:30 ` tromey at sourceware dot org
2023-11-30 17:15 ` tromey at sourceware dot org
2024-01-20 8:36 ` sam at gentoo dot org
2024-02-15 17:02 ` tromey at sourceware dot org
2025-02-04 15:38 ` josh.cottingham at linaro dot org [this message]
2025-02-05 10:15 ` josh.cottingham at linaro dot org
2025-02-20 22:23 ` tromey at sourceware dot org
2025-02-20 22:24 ` tromey at sourceware dot org
2025-02-21 16:27 ` tromey at sourceware dot org
2025-02-21 16:34 ` tromey at sourceware dot org
2025-02-22 0:40 ` tromey at sourceware dot org
2025-02-22 18:51 ` tromey at sourceware dot org
2025-03-08 0:15 ` cvs-commit at gcc dot gnu.org
2025-03-08 0:19 ` tromey at sourceware dot org
2025-03-08 18:18 ` sam at gentoo 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-31010-4717-y6cs1fFA3M@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).