Re: Add .gdb_index and CRC mismatch

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