[Rpm-ecosystem] rpm debugedit as a separate project?
Florian Weimer
fweimer at redhat.com
Mon Feb 22 09:11:40 UTC 2021
* Neal Gompa:
> On Sun, Feb 21, 2021 at 10:19 PM Mark Wielaard <mark at klomp.org> wrote:
>> The code in rpm debugedit only deals with 128, 160, 256, 384 or 512
>> bit build-id lengths. See the hashing algorithms it tries. So making
>> sure we support at least those lengths will make sure we don't regress
>> in support. If you find other lengths in use then I am sure we can
>> make the code deal with that.
>
> I'm pretty sure I recently saw something that wasn't in those sizes
> for Go, but I'll have to look again. The build-id support for these
> languages is kind of inconsistent. :(
I think those aren't GNU build-ids:
$ readelf -nW /usr/bin/go
Displaying notes found in: .note.go.buildid
Owner Data size Description
Go 0x00000053 Unknown note type: (0x00000004) description data: 69 69 77 57 6b 48 31 75 62 37 35 7a 42 71 73 33 45 52 74 2d 2f 52 33 4b 31 72 43 56 38 6c 4b 65 67 55 2d 56 79 67 7a 55 74 2f 39 5f 50 61 51 5f 4e 59 6e 53 46 7a 77 51 53 4a 4c 6c 68 74 2f 76 63 63 57 78 4f 37 6f 78 6e 32 52 56 33 46 38 6d 54 46 49
So the tools should be fine with that.
Thanks,
Florian
More information about the Rpm-ecosystem
mailing list