This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/23712] dwarf2read.c:9730: internal-error: void dw2_add_symbol_to_list(symbol*, pending**): Assertion `(*listhead) == NULL || (SYMBOL_LANGUAGE ((*listhead)->symbol[0]) == SYMBOL_LANGUAGE (symbol))' failed
- From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 28 Sep 2018 10:26:33 +0000
- Subject: [Bug gdb/23712] dwarf2read.c:9730: internal-error: void dw2_add_symbol_to_list(symbol*, pending**): Assertion `(*listhead) == NULL || (SYMBOL_LANGUAGE ((*listhead)->symbol[0]) == SYMBOL_LANGUAGE (symbol))' failed
- Auto-submitted: auto-generated
- References: <bug-23712-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23712
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Keith Seitz from comment #5)
> (In reply to Richard Biener from comment #4)
> > Eventually the assert()s can be weakened to allow "compatible enough" (same
> > hash, etc.) languages? I realize that allowing LTO-like mixed language
> > environments looks like a very much larger change in gdb than I thought.
> >
> > Though it looks like C and C++ use different symbol hashing... in fact all
> > but C++ seem to use default_search_name_hash ...
> >
> > And what's the issue here? Just store the hash alongside the entries and
> > then
> > the "only" issue is that gdb doesn't properly switch languages automatically
> > (PR23713) so user name lookups might fail spuriously.
>
> I just wanted to let you know that I am looking at fixing this once and
> for all, but I am on vacation until next week. I have the (good) beginnings
> of a patch for this.
That's great news!
--
You are receiving this mail because:
You are on the CC list for the bug.