From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/30772] New: dwarflint checking for specification recursion
Date: Wed, 16 Aug 2023 18:50:09 +0000 [thread overview]
Message-ID: <bug-30772-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30772
Bug ID: 30772
Summary: dwarflint checking for specification recursion
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
This idea comes from this thread:
https://sourceware.org/pipermail/gdb-patches/2023-August/201655.html
The idea is that if a DIE refers to itself via a chain
of DW_AT_specification (or the other ways a DIE can refer
to another), then dwarflint ought to warn, as recursion like
this is never valid.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-08-16 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 18:50 tromey at sourceware dot org [this message]
2023-08-16 19:29 ` [Bug tools/30772] " mark at klomp dot 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-30772-10460@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).