From: Dmitry Antipov <dantipov@nvidia.com>
To: <gdb@sourceware.org>
Subject: Add .gdb_index and CRC mismatch
Date: Thu, 01 Mar 2018 12:41:00 -0000 [thread overview]
Message-ID: <25596a27-77c0-238e-748c-3d972914abec@nvidia.com> (raw)
In-Reply-To: <CAH=s-PPFvDyaBrVE7tRrNstKnU-pjTDe1tdYA5qfxdWmR+0oQQ@mail.gmail.com>
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?
And why there is no CRC warning when I do 'add-symbol-file /xxx/yyy/lib/debug/libzzz.so [addr]' manually?
Dmitry
next prev parent reply other threads:[~2018-03-01 12:41 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 ` Dmitry Antipov [this message]
2018-03-01 21:05 ` Add .gdb_index and CRC mismatch Jan Kratochvil
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=25596a27-77c0-238e-748c-3d972914abec@nvidia.com \
--to=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