From: Alex Bennee <kernel-hacker@bennee.com>
To: gdb@sourceware.org
Subject: Manually checking build id in elf files
Date: Thu, 03 Sep 2009 13:03:00 -0000 [thread overview]
Message-ID: <b2cdc9f30909030603l7ae20355hcb5615b1387358c4@mail.gmail.com> (raw)
Hi,
I'm trying to track down a weird failure in oprofile due to bad CRC's
in debug files [1]. As has
been noted in the bug report gdb should complain. However I'm able to
load the symbol-file
with nary a harsh word from gdb. The manual says gdb uses one of two
methods to verify
a symbol file is the correct one. The second method mentions "Build
Id" and the ld man page
seems to imply I should see a "note" section in the library to
indicate the build id.
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
vnms@vnms:~$
Am I missing something? Is there a way to use readelf to read this information?
[1] https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/415424
--
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk
next reply other threads:[~2009-09-03 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 13:03 Alex Bennee [this message]
2009-09-03 13:11 ` Jan Kratochvil
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=b2cdc9f30909030603l7ae20355hcb5615b1387358c4@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=gdb@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