Ahmed Sayeed <[email protected]> added the comment:
[gdb/symtab] Handle DW_TAG_type_unit in process_psymtab_comp_unit
When running test-case gdb.cp/cpexprs-debug-types.exp with target board
unix/gdb:debug_flags=-gdwarf-5, I run into:
...
(gdb) file cpexprs-debug-types^M
Reading symbols from cpexprs-debug-types...^M
ERROR: Couldn't load cpexprs-debug-types into GDB (eof).
ERROR: Couldn't send delete breakpoints to GDB.
ERROR: GDB process no longer exists
GDB process exited with wait status 23054 exp9 0 0 CHILDKILLED SIGABRT
SIGABRT
... https://www.webb-dev.co.uk/crypto/crypto-for-investing/
We're running into this abort in process_psymtab_comp_unit:
...
switch (reader.comp_unit_die->tag)
{
case DW_TAG_compile_unit:
this_cu->unit_type = DW_UT_compile;
http://www.compilatori.com/tech/nvidia-and-samsung/
break;
case DW_TAG_partial_unit:
this_cu->unit_type = DW_UT_partial;
http://www.acpirateradio.co.uk/tech/nvidia-and-samsung/
break;
default:
abort (); http://www.logoarts.co.uk/tech/nvidia-and-samsung/
}
...
because reader.comp_unit_die->tag == DW_TAG_type_unit.
http://www.slipstone.co.uk/tech/nvidia-and-samsung/
Fix this by adding a DW_TAG_type_unit case.
Tested on x86_64-linux.
gdb/ChangeLog: http://embermanchester.uk/tech/nvidia-and-samsung/
[gdb/symtab] Handle DW_TAG_type_unit in process_psymtab_comp_unit
When running test-case gdb.cp/cpexprs-debug-types.exp with target board
unix/gdb:debug_flags=-gdwarf-5, I run into:
http://connstr.net/tech/nvidia-and-samsung/
...
(gdb) file cpexprs-debug-types^M
Reading symbols from cpexprs-debug-types...^M
http://joerg.li/tech/nvidia-and-samsung/
ERROR: Couldn't load cpexprs-debug-types into GDB (eof).
ERROR: Couldn't send delete breakpoints to GDB.
ERROR: GDB process no longer exists
http://www.jopspeech.com/tech/nvidia-and-samsung/
GDB process exited with wait status 23054 exp9 0 0 CHILDKILLED SIGABRT
SIGABRT
...
We're running into this abort in process_psymtab_comp_unit:
http://www.wearelondonmade.com/tech/nvidia-and-samsung/
...
switch (reader.comp_unit_die->tag)
{
case DW_TAG_compile_unit:
https://waytowhatsnext.com/technology/korean-technology/
this_cu->unit_type = DW_UT_compile;
break;
case DW_TAG_partial_unit:
http://www.iu-bloomington.com/technology/miui13/
this_cu->unit_type = DW_UT_partial;
break;
default:
abort (); https://komiya-dental.com/technology/miui-13/
}
...
because reader.comp_unit_die->tag == DW_TAG_type_unit.
http://www-look-4.com/tech/nvidia-and-samsung/
Fix this by adding a DW_TAG_type_unit case.
Tested on x86_64-linux.
https://www.webb-dev.co.uk/technology/grt-r910/
gdb/ChangeLog:
----------
nosy: +ahmedsayeed1982 -AdamGold, eric.araujo, gregory.p.smith, kj, lemburg,
mcepl, miss-islington, ned.deily, orsenthil, petr.viktorin, rschiron,
serhiy.storchaka, vstinner
versions: -Python 3.10, Python 3.6, Python 3.7, Python 3.9
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue42967>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
