Discussion:
[Bug symtab/23010] New: Assertion: SYMBOL_LANGUAGE (sym) == DICT_LANGUAGE (dict)->la_language
keiths at redhat dot com
2018-03-27 18:20:38 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Bug ID: 23010
Summary: Assertion: SYMBOL_LANGUAGE (sym) == DICT_LANGUAGE
(dict)->la_language
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: keiths at redhat dot com
Target Milestone: ---

A Fedora user reported a bug with the listed assertion. A reproducer is
specified there by Jan.

https://bugzilla.redhat.com/show_bug.cgi?id=1560010
--
You are receiving this mail because:
You are on the CC list for the bug.
jan.kratochvil at redhat dot com
2018-03-27 18:36:19 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jan.kratochvil at redhat dot com
Version|unknown |8.1
Target Milestone|--- |8.1.1
Summary|Assertion: SYMBOL_LANGUAGE |Regression: Assertion:
|(sym) == DICT_LANGUAGE |SYMBOL_LANGUAGE (sym) ==
|(dict)->la_language |DICT_LANGUAGE
| |(dict)->la_language
--
You are receiving this mail because:
You are on the CC list for the bug.
jan.kratochvil at redhat dot com
2018-04-12 17:50:25 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> ---
The regression is:
PASS: gdb-8.0
FAIL: gdb-8.1
--
You are receiving this mail because:
You are on the CC list for the bug.
tromey at sourceware dot org
2018-04-12 19:34:54 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
See https://sourceware.org/ml/gdb-patches/2018-04/msg00234.html
--
You are receiving this mail because:
You are on the CC list for the bug.
nolange79 at gmail dot com
2018-06-13 10:42:55 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

nolange79 at gmail dot com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |nolange79 at gmail dot com

--- Comment #5 from nolange79 at gmail dot com ---
Created attachment 11069
--> https://sourceware.org/bugzilla/attachment.cgi?id=11069&action=edit
program that causes the issue

With the fix applied, I still get the error, so this does not seem solved.
Can not manage to narrow it down, seems to involve gcc 8 + LTO atleast.
The file does run on debian, needs lttng-ust library.

Running the line below causes the trouble:

gdb -ex 'p sizeof (void*)' netfilter
--
You are receiving this mail because:
You are on the CC list for the bug.
cvs-commit at gcc dot gnu.org
2018-07-24 20:23:20 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Keith Seitz <***@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=380618d68a2b4ee60cebf3941d11a5af4e0aeee0

commit 380618d68a2b4ee60cebf3941d11a5af4e0aeee0
Author: Keith Seitz <***@redhat.com>
Date: Tue Jul 24 12:48:58 2018 -0700

Set CU language before processing any DIEs (symtab/23010 et al)

This patch is another attempt at really fixing the multitude of assertions
being seen where symbols of one language are being added to symbol lists of
another language.

In this specific case, the backtrace command (thread apply all bt full)
that
is looking for the compunit containing the PC of the thread. That calls
get_prev_frame several times. This function calls (eventually)
dwarf2_frame_prev_register. That eventually ends up calling
find_pc_compunit_symtab.

In this function (find_pc_sect_compunit_symtab actually), we loop over all
compunits, calling the "quick" function dw2_find_pc_sect_compunit_symtab.
That function calls dw2_instantiate_symtab to read in all the CU's symbols.
Now the fun begins.

dw2_do_instantiate_symtab queues the per_cu for reading, using a default
"pretend" language of language_minimal with the expectation that this will
be set later.

The DIEs of this (only queued) CU are then processed.

The first DIE is DW_TAG_compile_unit. That's handled by read_file_scope.

(Nearly) The first thing read_file_scope does is:

get_scope_pc_bounds (die, &lowpc, &highpc, cu);

This function loops over the children of the current DIE (a compile_unit),
looking for bounds. The first such child is a subprogram, and we attempt to
get its bounds. We use dwarf2_attr to get at DW_AT_high_pc.

This subprogram has DW_AT_specification set, so dwarf_attr (via
follow_die_ref/follow_die_offset) will follow that, but follow_die_offset
*also* attempts to load the containing CU for the spec DIE. That spec DIE
lives inside a CU that is a partial_unit and has no language attribute. So
it simply inherits the language from the CU that elicited the read. [That
all happens in follow_die_offset.]

The original CU's language is still language_minimal -- we haven't gotten
to
the line in read_file_scope that actually sets the language yet!

And that is the cause of these problems. The call to prepare_one_comp_unit
needs to be the *first* thing that is done when reading a CU so that the
CU's language can be recorded (and inherited by any referenced
partial_units).

Since a test reproducer for this has been so elusive, this patch also adds
a
wrapper function around add_symbol_to_list which asserts when adding a
symbol of one language to a list containing symbols of a different
language.

gdb/ChangeLog:
2017-07-24 Keith Seitz <***@redhat.com>

PR symtab/23010
* dwarf2read.c (dw2_add_symbol_to_list): New function.
(fixup_go_packaging, new_symbol): Use dw2_add_symbol_to_list
instead of add_symbol_to_list.
(read_file_scope): Call prepare_one_comp_unit before reading
any other DIEs.
--
You are receiving this mail because:
You are on the CC list for the bug.
cvs-commit at gcc dot gnu.org
2018-07-24 20:25:45 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-8.2-branch branch has been updated by Keith Seitz
<***@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9eb8d8e3e025323c9c5566b36c1fdc331aa33132

commit 9eb8d8e3e025323c9c5566b36c1fdc331aa33132
Author: Keith Seitz <***@redhat.com>
Date: Tue Jul 24 12:45:51 2018 -0700

Set CU language before processing any DIEs (symtab/23010 et al)

This patch is another attempt at really fixing the multitude of assertions
being seen where symbols of one language are being added to symbol lists of
another language.

In this specific case, the backtrace command (thread apply all bt full)
that
is looking for the compunit containing the PC of the thread. That calls
get_prev_frame several times. This function calls (eventually)
dwarf2_frame_prev_register. That eventually ends up calling
find_pc_compunit_symtab.

In this function (find_pc_sect_compunit_symtab actually), we loop over all
compunits, calling the "quick" function dw2_find_pc_sect_compunit_symtab.
That function calls dw2_instantiate_symtab to read in all the CU's symbols.
Now the fun begins.

dw2_do_instantiate_symtab queues the per_cu for reading, using a default
"pretend" language of language_minimal with the expectation that this will
be set later.

The DIEs of this (only queued) CU are then processed.

The first DIE is DW_TAG_compile_unit. That's handled by read_file_scope.

(Nearly) The first thing read_file_scope does is:

get_scope_pc_bounds (die, &lowpc, &highpc, cu);

This function loops over the children of the current DIE (a compile_unit),
looking for bounds. The first such child is a subprogram, and we attempt to
get its bounds. We use dwarf2_attr to get at DW_AT_high_pc.

This subprogram has DW_AT_specification set, so dwarf_attr (via
follow_die_ref/follow_die_offset) will follow that, but follow_die_offset
*also* attempts to load the containing CU for the spec DIE. That spec DIE
lives inside a CU that is a partial_unit and has no language attribute. So
it simply inherits the language from the CU that elicited the read. [That
all happens in follow_die_offset.]

The original CU's language is still language_minimal -- we haven't gotten
to
the line in read_file_scope that actually sets the language yet!

And that is the cause of these problems. The call to prepare_one_comp_unit
needs to be the *first* thing that is done when reading a CU so that the
CU's language can be recorded (and inherited by any referenced
partial_units).

Since a test reproducer for this has been so elusive, this patch also adds
a
wrapper function around add_symbol_to_list which asserts when adding a
symbol of one language to a list containing symbols of a different
language.

gdb/ChangeLog:
2017-07-24 Keith Seitz <***@redhat.com>

PR symtab/23010
* dwarf2read.c (dw2_add_symbol_to_list): New function.
(fixup_go_packaging, new_symbol): Use dw2_add_symbol_to_list
instead of add_symbol_to_list.
(read_file_scope): Call prepare_one_comp_unit before reading
any other DIEs.
--
You are receiving this mail because:
You are on the CC list for the bug.
lzsiga at freemail dot c3.hu
2018-08-02 10:58:23 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Lorinczy Zsigmond <lzsiga at freemail dot c3.hu> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |lzsiga at freemail dot c3.hu

--- Comment #8 from Lorinczy Zsigmond <lzsiga at freemail dot c3.hu> ---
I have the same problem on AIX 6, PowerPC, 64-bit, with gdb-8.1.1
--
You are receiving this mail because:
You are on the CC list for the bug.
keiths at redhat dot com
2018-08-02 16:07:44 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #9 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Lorinczy Zsigmond from comment #8)
Post by lzsiga at freemail dot c3.hu
I have the same problem on AIX 6, PowerPC, 64-bit, with gdb-8.1.1
"Target Milestone: 8.2"

The patch is not in 8.1[.x] as far as I know. Please try master or the 8.2
branch.

If the problem persists, I would be very anxious to get my hands on some way to
reproduce this.
--
You are receiving this mail because:
You are on the CC list for the bug.
lzsiga at freemail dot c3.hu
2018-08-02 21:13:23 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #10 from Lorinczy Zsigmond <lzsiga at freemail dot c3.hu> ---
T(In reply to Keith Seitz from comment #9)
Post by keiths at redhat dot com
The patch is not in 8.1[.x] as far as I know. Please try master or the 8.2
branch.
Hi, thank you for your quick answer. So far, I was not successful dowloading
version 8.2, maybe it is only for developers?

$ git clone --branch gdb-8.2-branch
ssh://sourceware.org/git/binutils-gdb.git
Cloning into 'binutils-gdb'...
***@sourceware.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
--
You are receiving this mail because:
You are on the CC list for the bug.
sergiodj at redhat dot com
2018-08-03 04:27:22 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |sergiodj at redhat dot com

--- Comment #11 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(In reply to Lorinczy Zsigmond from comment #10)
Post by lzsiga at freemail dot c3.hu
T(In reply to Keith Seitz from comment #9)
Post by keiths at redhat dot com
The patch is not in 8.1[.x] as far as I know. Please try master or the 8.2
branch.
Hi, thank you for your quick answer. So far, I was not successful dowloading
version 8.2, maybe it is only for developers?
$ git clone --branch gdb-8.2-branch
ssh://sourceware.org/git/binutils-gdb.git
Cloning into 'binutils-gdb'...
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Do you have an account on sourceware? If not, then using ssh:// to clone the
repository will not work. You should use git://.
--
You are receiving this mail because:
You are on the CC list for the bug.
lzsiga at freemail dot c3.hu
2018-08-03 09:17:18 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #12 from Lorinczy Zsigmond <lzsiga at freemail dot c3.hu> ---
(In reply to Sergio Durigan Junior from comment #11)
Post by sergiodj at redhat dot com
Do you have an account on sourceware? If not, then using ssh:// to clone
the repository will not work. You should use git://.
Thank you, now I was able compile it. Well, the problem persists, I'll try to
debug it, so far here is some bits I collected:
OS: Aix-6.1; CPU: PowerPC (64-bit, big endian); C-compiler: gcc 4.8.3;
how to provoke the failure: the program-to-be-debugged have to depend on an
external shared object compiled with gcc:

$ gdb ./helloworld
GNU gdb (GDB) 8.1.90.20180803-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "powerpc-ibm-aix6.1.9.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./helloworld...done.
dictionary.c:690: internal-error: void insert_symbol_hashed(dictionary*,
symbol*): Assertion `SYMBOL_LANGUAGE (sym) == DICT_LANGUAGE
(dict)->la_language' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

dictionary.c:690: internal-error: void insert_symbol_hashed(dictionary*,
symbol*): Assertion `SYMBOL_LANGUAGE (sym) == DICT_LANGUAGE
(dict)->la_language' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb) quit
--
You are receiving this mail because:
You are on the CC list for the bug.
tromey at sourceware dot org
2018-08-08 11:47:13 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Tom Tromey <tromey at sourceware dot org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---

--- Comment #13 from Tom Tromey <tromey at sourceware dot org> ---
Reopening, since it's reported as not fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
lzsiga at freemail dot c3.hu
2018-08-11 10:18:54 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #14 from Lorinczy Zsigmond <lzsiga at freemail dot c3.hu> ---
Hi, I am still trying to collect information, here is what I have so far:
https://www.linuxquestions.org/questions/aix-43/gdb-8-1-1-versus-aix-4175636082/
--
You are receiving this mail because:
You are on the CC list for the bug.
rdiezmail-binutils at yahoo dot de
2018-08-14 14:31:39 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

rdiezmail-binutils at yahoo dot de changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |rdiezmail-binutils at yahoo dot de
--
You are receiving this mail because:
You are on the CC list for the bug.
lzsiga at freemail dot c3.hu
2018-08-14 15:28:39 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #15 from Lorinczy Zsigmond <lzsiga at freemail dot c3.hu> ---
Well, it's just a wild guess, but my problem might be related with the fact,
that every call of 'start_symtab' in 'xcoffread.c' passes parameter 'language'
as 'language_unknown'
--
You are receiving this mail because:
You are on the CC list for the bug.
keiths at redhat dot com
2018-08-14 15:35:58 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #16 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Lorinczy Zsigmond from comment #15)
Post by lzsiga at freemail dot c3.hu
Well, it's just a wild guess, but my problem might be related with the fact,
that every call of 'start_symtab' in 'xcoffread.c' passes parameter
'language' as 'language_unknown'
That's what the DWARF reader does, too. The problem is that symbols are being
added to the dictionary *before* the real language is read from the debug info.
[For a detailed explanation of what was happening in the DWARF reader, see
comment #7. Something similar *must* be happening here.]

If you can provide me with a reproducer, the GCC compile farm has an s390 box
(or two) that I can use to debug this.
--
You are receiving this mail because:
You are on the CC list for the bug.
rdiezmail-binutils at yahoo dot de
2018-08-14 18:46:11 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #17 from rdiezmail-binutils at yahoo dot de ---
I recently hit this issue with the following open-source project of mine:

https://github.com/rdiez/JtagDue

That project has a Toolchain/ subdir with the script I use to build a GCC-based
toolchain. I have used it for years, upgrading GCC etc. every now and then.

With GCC 7.3 and GDB 8.1 I had no problem, but when I tried to upgrade to GCC
8.2, I got the assertion straight away. I had never seen this assertion in the
past.

Unfortunately, it is a cross-compiler for a Cortex-M3 embedded target, so it
does not run on a normal PC.

If you are having trouble reproducing this issue, I could try again with the
HEAD sources. Just tell me what flags I should build GDB with, and how to
extract the information you need to debug the assertion.
--
You are receiving this mail because:
You are on the CC list for the bug.
tromey at sourceware dot org
2018-08-14 19:43:33 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #18 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to rdiezmail-binutils from comment #17)
Post by rdiezmail-binutils at yahoo dot de
If you are having trouble reproducing this issue, I could try again with the
HEAD sources. Just tell me what flags I should build GDB with, and how to
extract the information you need to debug the assertion.
Does gdb crash with just the executable? Like, do you need to actually
run the program? Or does it crash with -readnow?
If so then just getting the executable would help.
--
You are receiving this mail because:
You are on the CC list for the bug.
rdiezmail-binutils at yahoo dot de
2018-08-14 14:22:50 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #19 from rdiezmail-binutils at yahoo dot de ---
My scripts run the executable on the target straight away. I did not check how
far GDB got when it asserted. I'll build a new toolchain and try again
tomorrow.
--
You are receiving this mail because:
You are on the CC list for the bug.
rdiezmail-binutils at yahoo dot de
2018-08-15 07:45:32 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #20 from rdiezmail-binutils at yahoo dot de ---
Created attachment 11184
--> https://sourceware.org/bugzilla/attachment.cgi?id=11184&action=edit
ELF file that makes GDB assert
--
You are receiving this mail because:
You are on the CC list for the bug.
rdiezmail-binutils at yahoo dot de
2018-08-15 02:16:53 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #21 from rdiezmail-binutils at yahoo dot de ---
OK, I can still reproduce the problem:

-----8<-----8<-----8<-----

GNU gdb (GDB) 8.1.90.20180815-git
[... blah blah ...]
Reading symbols from
/home/rdiez/rdiez/arduino/JtagDue/BuildOutput/JtagDue-obj-release/firmware.elf...done.
(gdb) p SysTick_Handler
dwarf2read.c:9715: internal-error: void dw2_add_symbol_to_list(symbol*,
pending**): Assertion `(*listhead) == NULL || (SYMBOL_LANGUAGE
((*listhead)->symbol[0]) == SYMBOL_LANGUAGE (symbol))' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

-----8<-----8<-----8<-----

There is no need to run the firmware, just loading the ELF in GDB and trying to
print the function above breaks it.

This only happens with the release build of my firmware, which is built with
LTO. The debug build works fine.

I built GDB like this:

cd "$HOME/rdiez/temp/gdb-8.2-branch" && ./configure CFLAGS="-O0 -g"
CXXFLAGS="-O0 -g" --prefix="$HOME/rdiez/temp/gdb-8.2-branch-bin"
--target=arm-none-eabi

I have attached file firmware.elf to this bug.

What else do you need?
--
You are receiving this mail because:
You are on the CC list for the bug.
keiths at redhat dot com
2018-08-15 21:35:38 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #22 from Keith Seitz <keiths at redhat dot com> ---
(In reply to rdiezmail-binutils from comment #21)
Post by rdiezmail-binutils at yahoo dot de
This only happens with the release build of my firmware, which is built with
LTO. The debug build works fine.
cd "$HOME/rdiez/temp/gdb-8.2-branch" && ./configure CFLAGS="-O0 -g"
CXXFLAGS="-O0 -g" --prefix="$HOME/rdiez/temp/gdb-8.2-branch-bin"
--target=arm-none-eabi
I have attached file firmware.elf to this bug.
What else do you need?
I can confirm that this is reproduced on my "normal" --enable-targets=all
builds on Fedora. I will investigate.
--
You are receiving this mail because:
You are on the CC list for the bug.
brobecker at gnat dot com
2018-08-21 12:11:32 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

Joel Brobecker <brobecker at gnat dot com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |brobecker at gnat dot com

--- Comment #23 from Joel Brobecker <brobecker at gnat dot com> ---
Can we verify whether the problem reproduces with 8.0 or not? Knowing whether
this is indeed a regression would help prioritize a bit, which we need to do,
as 8.2 is getting farther and farther behind the tentative schedule.

Thank you!
--
You are receiving this mail because:
You are on the CC list for the bug.
keiths at redhat dot com
2018-08-24 18:31:12 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #24 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Joel Brobecker from comment #23)
Post by brobecker at gnat dot com
Can we verify whether the problem reproduces with 8.0 or not? Knowing
whether this is indeed a regression would help prioritize a bit, which we
need to do, as 8.2 is getting farther and farther behind the tentative
schedule.
The patch series that introduced this problem is cxx-breakpoint-improvements.
That series was committed in November 2017 -- after 8.0 was released.

For what little it is worth, the problems that rdiezmail-binutils is reporting
is specifically a result of using LTO. GCC outputs an artificial compile_unit
DIE (language_c) and then inlines functions from C++ compilation units,
triggering the assertion. I'm still playing with ideas to solve this.

The AIX problem reported by Lorinczy Zsigmond, however, hints at hiding
problems in other debuginfo readers.
--
You are receiving this mail because:
You are on the CC list for the bug.
keiths at redhat dot com
2018-10-26 14:28:15 UTC
Permalink
https://sourceware.org/bugzilla/show_bug.cgi?id=23010

--- Comment #25 from Keith Seitz <keiths at redhat dot com> ---
There is a patch that has been approved for AIX. It is a slightly different
problem than what is causing grief on DWARF-using systems, but it triggers the
same DICT_LANGUAGE == SYMBOL_LANGUAGE assertion failure:

https://sourceware.org/ml/gdb-patches/2018-10/msg00324.html
--
You are receiving this mail because:
You are on the CC list for the bug.
Loading...