GDB 8.2 fails to load LTO applications
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Arm Embedded Toolchain |
New
|
Undecided
|
Unassigned |
Bug Description
The problem occurs with gcc-arm-
It is an assert related to dwarf and occurs while GDB tries to load an .elf that was compiled with -flto.
Retaining the latest version of the compiler but reverting only GDB to the previous version (GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.
The GDB trace captured by Eclipse is below.
Any suggestions how to proceed? Report this via the GNU bugzilla?
Regards,
Liviu
551,953 &"symbol-file /Users/
lf\n"
551,953 ~"Reading symbols from /Users/
to-test.elf...\n"
551,962 30^done
551,962 (gdb)
551,964 &"load /Users/
551,964 ~"Loading section .isr_vector, size 0x3bc lma 0x8000000\n"
551,966 31+download,
551,966 31+download,
tal-size="934014"}
551,966 ~"Loading section .inits, size 0x28 lma 0x80003bc\n"
551,968 31+download,
551,968 ~"Loading section .text, size 0xcf3 lma 0x80003f0\n"
551,968 31+download,
551,968 ~"Loading section .data, size 0x74 lma 0x80010e4\n"
551,969 31+download,
551,969 ~"Start address 0x80002a4, load size 4427\n"
552,406 ~"Transfer rate: 864 KB/sec, 1106 bytes/write.\n"
552,407 ~"/tmp/
ead.c:9809: internal-error: void dw2_add_
on `(*listhead) == NULL || (SYMBOL_LANGUAGE ((*listhead)
ailed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit \
this debugging session? "
552,408 ~"(y or n) [answered Y; input not from terminal]\n"
552,408 &"\nThis is a bug, please report it."
552,408 &" For instructions, see:\n<http://
552,408 &"\n\n"
552,408 ~"/tmp/
ead.c:9809: internal-error: void dw2_add_
on `(*listhead) == NULL || (SYMBOL_LANGUAGE ((*listhead)
ailed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nCreat\
e a core file of GDB? "
552,409 ~"(y or n) [answered Y; input not from terminal]\n"
tags: | added: ice |
In this case please file a bug upstream in the gdb bugzilla. Is the same issue occurring on a linux host and could you please put up a testcase (source and binaries) that folks could use to reproduce the issue ?