From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH] [gdb/symtab] Handle self-reference DIE
Date: Wed, 16 Aug 2023 12:51:22 -0600 [thread overview]
Message-ID: <87o7j6yg5x.fsf@tromey.com> (raw)
In-Reply-To: <20230816125602.23696-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Wed, 16 Aug 2023 14:56:02 +0200")
>>>>> Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
> Fix this by inhibiting the scan_attributes self-recursion for self-references.
Makes sense, thanks.
Approved-By: Tom Tromey <tom@tromey.com>
> Note that this doesn't fix the same problems for the more complicated case of:
> ...
> <1><be>: Abbrev Number: 3 (DW_TAG_class_type)
> <bf> DW_AT_name : c1
> <c2> DW_AT_specification: <0xc6>
> <1><c6>: Abbrev Number: 4 (DW_TAG_class_type)
> <c7> DW_AT_name : c2
> <ca> DW_AT_specification: <0xbe>
> ...
> but the approach for deciding whether to fix pathological dwarf cases is as
> per PR27981 comment 3:
> ...
> yes if it is cheap/obvious, and no if it is something complicated or expensive.
> ...
> and at this point I'm not sure whether fixing this will fall in the first
> category.
I suspect full recursion detection would be too expensive.
However, one idea would be to limit the number of specifications that
would be followed. A small limit like 4 or 5 is probably more than
enough for all actually-existing DWARF.
I filed a dwarflint bug for this:
https://sourceware.org/bugzilla/show_bug.cgi?id=30772
Tom
prev parent reply other threads:[~2023-08-16 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 12:56 Tom de Vries
2023-08-16 18:51 ` Tom Tromey [this message]
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=87o7j6yg5x.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).