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/30822] New: [gdb/symtab] Handle cyclic DIE references
Date: Mon, 04 Sep 2023 11:41:30 +0000	[thread overview]
Message-ID: <bug-30822-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30822
           Summary: [gdb/symtab] Handle cyclic DIE references
           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: ---

There are a few fixes in place in gdb/dwarf2/read.c that deal with
self-referencing DIEs:
...
$ grep -i self-ref gdb/dwarf2/read.c
              /* Handle DIE with self-reference.  */
      /* Self-referential typedefs are, it seems, not allowed by the DWARF
      complaint (_("Self-referential DW_TAG_typedef "
              /* Self-reference, we're done.  */
        /* Self-reference, we're done.  */
      /* Self-reference, we're done.  */
...

These prevent either a hang or running out of stack.

The generic case of cyclic DIE references (for instance DIE A references DIE B,
DIE B references DIE A) hasn't been solved though.

Tom Tromey mentioned using a tortoise/hare approach to detect the cycles here (
https://sourceware.org/pipermail/gdb-patches/2023-August/201921.html ).

See https://en.wikipedia.org/wiki/Cycle_detection#Floyd's_tortoise_and_hare .

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

                 reply	other threads:[~2023-09-04 11:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-30822-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: 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).