Re: [PATCH] gdb: defer warnings when loading separate debug files

[fche@redhat.com (Frank Ch. Eigler)]

Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:

> [...]
> I don't really like this behavior change.  The situations you described:
>
>  - a separate debug file without any actual debug information
>  - CRC checksum that doesn't match
>
> ... are abnormal situations which still deserve being warned about, I
> think.  If the files are there, it's because they are meant to be
> used,

That's a bit of a leap.  They can happen totally accidentally, when a
sysadmin or cron job does an automated update of the system, and for
whatever reason, the debug packages got missed.  On some distros, this
can easily happen.  Then the remnants are not "meant to be used" at all,
they are just fossils.

> so if something prevents GDB from using them, I want to know.
> Silencing the warning just makes investigating "why doesn't GDB read
> my separate debug file" harder.

If GDB did find the correct debug file one way or the other, then why
would you care, never mind bother investigate?  It's a non-problem.


> I can understand why this can be a bit confusing to the user, but
> the warning is still factually correct.  For instance, the one you
> quoted:
>
>     warning: the debug information found in
>     "/usr/lib/debug//lib64/ld-2.32.so.debug" does not match
>     "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

Ideally, users should really only be warned about things that they can
do something about.  Being warned about the same thing that only a
sysadmin can possibly fix, and repeatedly, seems more like noise.

- FChE