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/30799] [gdb/symtab] hang in inherit_abstract_dies
Date: Mon, 28 Aug 2023 14:27:39 +0000	[thread overview]
Message-ID: <bug-30799-4717-ecikB3eTB6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30799-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30799

--- Comment #3 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=8d83f51b91072bc3d79061eba7e564ba9be6afd7

commit 8d83f51b91072bc3d79061eba7e564ba9be6afd7
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Aug 28 16:27:58 2023 +0200

    [gdb/symtab] Handle self-reference in inherit_abstract_dies

    Building gdb with gcc 7.5.0 and -flto -O2 -flto-partition=one generates a
    self-referencing DIE:
    ...
     <2><91dace>: Abbrev Number: 405 (DW_TAG_label)
        <91dad0>   DW_AT_abstract_origin: <0x91dace>
    ...

    When encountering the self-reference DIE in inherit_abstract_dies we loop
    following the abstract origin, effectively hanging gdb.

    Fix this by handling self-referencing DIEs in the loop in
    inherit_abstract_dies.

    Tested on x86_64-linux.

    Approved-By: Tom Tromey <tom@tromey.com>

    PR symtab/30799
    https://sourceware.org/bugzilla/show_bug.cgi?id=30799

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-28 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28  4:24 [Bug symtab/30799] New: " vries at gcc dot gnu.org
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 [this message]
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-ecikB3eTB6@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: link
Be 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).