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 14:24:00 -0000 [thread overview]
Message-ID: <20090903142440.GA32443@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <b2cdc9f30909030645g465bccfbx977072b16953353c@mail.gmail.com>
On Thu, 03 Sep 2009 15:45:32 +0200, Alex Bennee wrote:
> My version is:
> $ eu-readelf --version
> readelf (Red Hat elfutils) 0.131
This version should already have the build-id support.
> Which makes me wonder why gdb is allowing the load of the symbol file given:
Explicit `symbol-file' command will load it as it can load arbitrary file for
the symbols. Automatic finding of the associated separate debug info files
(find_separate_debug_file) ignores any files with non-matching build-id or
CRC32.
> 1. There seems to be no build ID
Yes, I think your mail has nothing to do with build-id.
> 2. The CRC in the library doesn't match the CRC of the library.debug
In the Bug it is shown libc has correct CRC32 but libcairo does not.
Regards,
Jan
next prev parent reply other threads:[~2009-09-03 14:24 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
2009-09-03 13:45 ` Alex Bennee
2009-09-03 14:24 ` Jan Kratochvil [this message]
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=20090903142440.GA32443@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