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: "keiths at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 27 Sep 2018 14:27:52 +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
Keith Seitz <keiths at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |keiths at redhat dot com
--- Comment #5 from Keith Seitz <keiths at redhat dot com> ---
(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.
Alas, there is a recent patch on HEAD that is causing problems for me
and will require further investigation.
--
You are receiving this mail because:
You are on the CC list for the bug.