public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/27333] [dwarf-5] abort on unhandled DW_TAG_type_unit in process_psymtab_comp_unit Date: Fri, 05 Feb 2021 16:47:17 +0000 [thread overview] Message-ID: <bug-27333-4717-ehirWXELHE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27333-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27333 --- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e77b0004dd114d6ddf3bb92b521b2854341f3f85 commit e77b0004dd114d6ddf3bb92b521b2854341f3f85 Author: Tom de Vries <tdevries@suse.de> Date: Fri Feb 5 17:47:07 2021 +0100 [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 ... 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; break; case DW_TAG_partial_unit: this_cu->unit_type = DW_UT_partial; break; default: abort (); } ... because reader.comp_unit_die->tag == DW_TAG_type_unit. Fix this by adding a DW_TAG_type_unit case. Tested on x86_64-linux. gdb/ChangeLog: 2021-02-05 Tom de Vries <tdevries@suse.de> PR symtab/27333 * dwarf2/read.c (process_psymtab_comp_unit): Handle DW_TAG_type_unit. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-05 16:47 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-03 11:55 [Bug symtab/27333] New: [dwarf-5] ERROR: Couldn't load cpexprs-debug-types into GDB (eof) vries at gcc dot gnu.org 2021-02-03 12:54 ` [Bug symtab/27333] " vries at gcc dot gnu.org 2021-02-03 12:55 ` [Bug symtab/27333] [dwarf-5] abort on unhandled DW_TAG_type_unit in process_psymtab_comp_unit vries at gcc dot gnu.org 2021-02-03 13:05 ` vries at gcc dot gnu.org 2021-02-05 12:31 ` vries at gcc dot gnu.org 2021-02-05 16:47 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-05 16:48 ` vries at gcc dot gnu.org 2021-03-06 6:28 ` brobecker at gnat dot com 2021-03-06 6:34 ` cvs-commit at gcc dot gnu.org 2021-06-27 17:56 ` ahmedsayeed1982 at yahoo dot com 2021-08-19 6:01 ` ucelsanicin at yahoo dot com 2021-08-27 18:01 ` ribevi6798 at enamelme dot com 2021-09-02 11:07 ` donipah907 at mtlcz dot com 2021-09-02 11:14 ` mark at klomp dot org 2021-09-06 9:09 ` focixujo at livinginsurance dot co.uk 2021-09-10 19:39 ` mehmetgelisin at aol dot com 2021-09-22 10:10 ` diheto5497 at secbuf dot com 2021-09-26 13:31 ` tes.vik1986 at gmail dot com 2021-09-28 0:48 ` marlenesanchez231+jaime at gmail dot com 2021-10-09 11:00 ` gulsenenginar at aol dot com 2021-10-10 16:10 ` oficaj3 at gmail dot com 2021-10-18 19:58 ` ahmedsayeed1982 at hotmail dot com 2021-10-19 7:14 ` progonsaytu at gmail dot com 2021-10-23 13:47 ` fiteva5725 at bomoads dot com 2021-10-24 10:02 ` glassmtech at ukr dot net 2021-11-06 21:12 ` paneki8601 at dukeoo dot com 2021-11-13 19:33 ` tesaso8237 at funboxcn dot com 2021-11-16 19:04 ` xecana8007 at funboxcn dot com 2021-11-16 19:08 ` xecana8007 at funboxcn dot com 2021-11-16 19:12 ` xecana8007 at funboxcn dot com 2021-11-16 19:15 ` xecana8007 at funboxcn dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-27333-4717-ehirWXELHE@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).