From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: gdb@sourceware.org
Subject: Re: Manually checking build id in elf files
Date: Thu, 03 Sep 2009 13:11:00 -0000 [thread overview]
Message-ID: <20090903131100.GA27450@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <b2cdc9f30909030603l7ae20355hcb5615b1387358c4@mail.gmail.com>
On Thu, 03 Sep 2009 15:03:05 +0200, Alex Bennee wrote:
> I'd like to manually check it but readelf doesn't show any such notes:
>
> vnms@vnms:~$ readelf -n /usr/lib/libcairo.so.2.17.3
> vnms@vnms:~$ readelf -n /usr/lib/debug/usr/lib/libcairo.so.2.17.3
Try elfutils:
# eu-readelf -n /lib64/libc.so.6
Note section [ 1] '.note.gnu.build-id' of 36 bytes at offset 0x270:
Owner Data size Type
GNU 20 GNU_BUILD_ID
Build ID: ec8dd400904ddfcac8b1c343263a790f977159dc
[...]
# eu-unstrip -n -e /lib64/libc.so.6
0x3979600000+0x36d868 ec8dd400904ddfcac8b1c343263a790f977159dc@0x3979600280 /lib64/libc.so.6 /usr/lib/debug/lib64/libc-2.10.1.so.debug
> Am I missing something? Is there a way to use readelf to read this information?
From binutils you can use objdump:
# objdump -s -j .note.gnu.build-id /lib64/libc.so.6
[...]
Contents of section .note.gnu.build-id:
3979600270 04000000 14000000 03000000 474e5500 ............GNU.
----------->
3979600280 ec8dd400 904ddfca c8b1c343 263a790f .....M.....C&:y.
3979600290 977159dc .qY.
Regards,
Jan
next prev parent reply other threads:[~2009-09-03 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 13:03 Alex Bennee
2009-09-03 13:11 ` Jan Kratochvil [this message]
2009-09-03 13:45 ` Alex Bennee
2009-09-03 14:24 ` Jan Kratochvil
2009-09-03 14:47 ` Andreas Schwab
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=20090903131100.GA27450@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=kernel-hacker@bennee.com \
/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