From: Andreas Schwab <schwab@redhat.com>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Re: Manually checking build id in elf files
Date: Thu, 03 Sep 2009 14:47:00 -0000 [thread overview]
Message-ID: <m31vmo9jbx.fsf@hase.home> (raw)
In-Reply-To: <b2cdc9f30909030645g465bccfbx977072b16953353c@mail.gmail.com> (Alex Bennee's message of "Thu, 3 Sep 2009 14:45:32 +0100")
Alex Bennee <kernel-hacker@bennee.com> writes:
> Which makes me wonder why gdb is allowing the load of the symbol file given:
>
> 1. There seems to be no build ID
> 2. The CRC in the library doesn't match the CRC of the library.debug
The CRC is stored in the .gnu_debuglink section.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
prev parent reply other threads:[~2009-09-03 14:47 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
2009-09-03 14:47 ` Andreas Schwab [this message]
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=m31vmo9jbx.fsf@hase.home \
--to=schwab@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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