public inbox for
 help / color / mirror / Atom feed
From: "vries at gcc dot" <>
Subject: [Bug default/25462] New: [dwz] Include producer information in compressed file
Date: Wed, 01 Jan 2020 00:00:00 -0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 25462
           Summary: [dwz] Include producer information in compressed file
           Product: dwz
           Version: unspecified
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: default
          Assignee: nobody at sourceware dot org
          Reporter: vries at gcc dot
                CC: dwz at sourceware dot org
  Target Milestone: ---

It would be good to have a possibility to include information in the compressed
file about how that file was obtained (see f.i. PR25459 with the mystery
clang-offload-bundler-10.debug file).

We could f.i. add a dummy CU with a partial_unit DIE and a DW_AT_producer. [ It
would be nicer if we could store it somewhere outside the debug sections, but
I'm not sure where. ]

Info we may want:
- verbatim command line
- values of command line controlled variables (since defaults may
  change and are not visible on the command line)
- md5sum of input file (and/or md5sums of .debug sections)
- unique identifier of sources that were used (f.i. git hash)

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

             reply	other threads:[~2020-01-26  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01  0:00 vries at gcc dot [this message]
2020-01-01  0:00 ` [Bug default/25462] " vries at gcc dot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).