public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/25368] New: handle native golang buildids
Date: Fri, 10 Jan 2020 19:48:00 -0000	[thread overview]
Message-ID: <bug-25368-10460@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 25368
           Summary: handle native golang buildids
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: fche at redhat dot com
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

Native golang puts unique buildids into a .note.go.buildid section, with a much
longer textual string than our normal 20-byte blob.  debuginfod would need to
add these to the index, and golang debuginfo consumers would have to learn to
pass it.  hex-encoding the textual golang buildid should make it fit right into
the webapi, instead of worrying about '/' characters embedded inside.

RHEL packaged golang binaries get a normal gnu-style buildid also as a part of
package postprocessing, so this functionality may not be required there.

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

             reply	other threads:[~2020-01-10 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 19:48 fche at redhat dot com [this message]
2022-05-27 15:08 ` [Bug debuginfod/25368] " nsanci at redhat dot com
2022-05-27 15:16 ` nsanci at redhat dot com

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