From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: debugedit@sourceware.org
Subject: [Bug debugedit/27915] Cannot handle 8-byte build ID
Date: Wed, 26 May 2021 12:50:25 +0000 [thread overview]
Message-ID: <bug-27915-13298-yQ1H9vrAJS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27915-13298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27915
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> ---
(In reply to Matthias Klose from comment #0)
> Cannot handle 8-byte build ID
An 8-byte (just 64bits) build ID doesn't make much sense.
It is too small to make sure it is a globally unique identifier.
You need 16 bytes (128 bits) minimum.
This must be a linker bug. Older lld had a bug where they had a "fast" build-id
generator that produced such small (useless) build-ids.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-26 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 9:45 [Bug debugedit/27915] New: " doko at debian dot org
2021-05-26 12:50 ` mark at klomp dot org [this message]
2021-05-26 14:16 ` [Bug debugedit/27915] " doko at debian dot org
2021-05-26 14:24 ` 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-27915-13298-yQ1H9vrAJS@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=debugedit@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).