From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/30772] dwarflint checking for specification recursion
Date: Wed, 16 Aug 2023 19:29:29 +0000 [thread overview]
Message-ID: <bug-30772-10460-DhHKJapLO3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30772-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30772
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
libdw dwarf_attr_integrate does prevent cycles by limiting the chain of
DW_AT_abstract_origin and DW_AT_specification to 16 (arbitrary number).
On a different level, DW_AT_import can also create cycles (or rather infinite
imports). __libdw_visit_scopes does contain some cycle detection.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-08-16 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:50 [Bug tools/30772] New: " tromey at sourceware dot org
2023-08-16 19:29 ` mark at klomp dot org [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=bug-30772-10460-DhHKJapLO3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).