public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/30799] New: [gdb/symtab] hang in inherit_abstract_dies Date: Mon, 28 Aug 2023 04:24:08 +0000 [thread overview] Message-ID: <bug-30799-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30799 Bug ID: 30799 Summary: [gdb/symtab] hang in inherit_abstract_dies Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I build gdb with gcc 7.5.0 and -O2 -flto -flto-partition=one, and ran into timeouts in gdb.gdb/*.exp. The hang seems to be related to a self-referencing DIE: ... <2><91dace>: Abbrev Number: 405 (DW_TAG_label) <91dad0> DW_AT_abstract_origin: <0x91dace> ... We're stuck in this loop in inherit_abstract_dies: ... /* For each CHILD_DIE, find the corresponding child of ORIGIN_DIE. If there is more than one layer of DW_AT_abstract_origin, follow them all; there shouldn't be, but GCC versions at least through 4.4 generate this (GCC PR 40573). */ die_info *child_origin_die = child_die; dwarf2_cu *child_origin_cu = cu; while (true) { attr = dwarf2_attr (child_origin_die, DW_AT_abstract_origin, child_origin_cu); if (attr == nullptr) break; child_origin_die = follow_die_ref (child_origin_die, attr, &child_origin_cu); } ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-08-28 4:24 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-28 4:24 vries at gcc dot gnu.org [this message] 2023-08-28 4:25 ` [Bug symtab/30799] " vries at gcc dot gnu.org 2023-08-28 6:36 ` vries at gcc dot gnu.org 2023-08-28 14:27 ` cvs-commit at gcc dot gnu.org 2023-08-28 14:28 ` vries at gcc dot gnu.org
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-30799-4717@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).