From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Dmitry Antipov <dantipov@nvidia.com>
Cc: gdb@sourceware.org
Subject: Re: Add .gdb_index and CRC mismatch
Date: Thu, 01 Mar 2018 21:05:00 -0000 [thread overview]
Message-ID: <20180301210512.GA26517@host1.jankratochvil.net> (raw)
In-Reply-To: <25596a27-77c0-238e-748c-3d972914abec@nvidia.com>
On Thu, 01 Mar 2018 13:41:37 +0100, Dmitry Antipov wrote:
> For the remote debugging and local copies of shared libraries, should .so CRC be affected by
> adding .gdb_index as described at https://sourceware.org/gdb/onlinedocs/gdb/Index-Files.html?
> After adding .gdb_index, 'target extended-remote :XXXX' refuses to load local copy with
> the following message:
>
> warning: the debug information found in "/xxx/yyy/lib/debug/libzzz.so" does not match "target:/lib/libzzz.so" (CRC mismatch).
>
> If CRC was actually changed, how is it indented to use .gdb_index for the remote debugging?
At least in Fedora the separate .debug files are also processed by dwz and
then the CRC is updated by:
/usr/lib/rpm/sepdebugcrcfix
I was expecting the CRC update is needed for dwz and so gdb-add-index does not
contain this functionality. But you are right it should.
Besides that GDB prefers much faster verification of a .debug file match by
its build-id also being used on Fedora (ld --build-id). Then sure CRC is not
being checked (as that is slow to check).
Jan
prev parent reply other threads:[~2018-03-01 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 12:53 Both GCC and GDB buildbot use gcc114 Yao Qi
2018-02-27 21:46 ` Paulo Matos
2018-02-28 9:12 ` Yao Qi
2018-03-01 12:41 ` Add .gdb_index and CRC mismatch Dmitry Antipov
2018-03-01 21:05 ` Jan Kratochvil [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=20180301210512.GA26517@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dantipov@nvidia.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