Re: Warning when using separate debug info file

[Tom Tromey <tom at tromey dot com>]

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

>> The hypothesis is...actually, no, i have no idea. I mean, it's obvious that gdb
>> expects to find that section in a separate debug file for some reason. Probably
>> because separate debug files are just PE binaries, and the code that reads them
>> is heavily re-used. Or maybe gdb supports recursive debuglinks?

Eli> But then why doesn't this happen on GNU/Linux?

Those platforms moved away from the .gnu_debuglink approach to use
build-id instead.  See (info "(gdb) Separate Debug Files")

I don't really recall how .gnu_debuglink works, but I am somewhat
surprised to hear it should be in the separate debug file.  My
understanding of it was that it recorded a CRC and the verification
happened by computing the CRC of the separate debug file (this is
expensive, which is why build-id is superior...).

So I suppose this is just a bug but the cause remains unknown.

Tom