From: Alexandra Petlanova Hajkova <ahajkova@redhat.com>
To: gdb-patches@sourceware.org
Subject: Fwd: [PATCH] gdb: defer warnings when loading separate debug files
Date: Mon, 19 Dec 2022 13:28:54 +0100 [thread overview]
Message-ID: <CAJVr-EP5T21eKcZ8vd0ka5kruL-qTB21L_PXnwpy9EbuSnW3pg@mail.gmail.com> (raw)
In-Reply-To: <CAJVr-EOShPVS_ZBvfHqKkbPK1O3d+92DDbpEoeBVr1_s7_XWYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]
>
> 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,
> 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.
>
> 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).
>
> This doesn't say that GDB didn't end up finding *some* debug info for
> the shared object, just that this particular one is broken. Maybe it's
> an old one I installed by hand, that I should delete, maybe the package
> from the distro is broken. In any case it's good for the user to know
> so they can fix the situation.
>
> Simon
>
> Yes, it's a good point. It might be confusing to see the warnings if the
correct debuginfo was retrieved but it might be useful to see all the
warnings
on the other hand. I would love to have more opinions on this matter.
Thank you,
Alexandra
next prev parent reply other threads:[~2022-12-19 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 12:15 AlexandraH=?UTF-8?B?w6E=?=jkov=?UTF-8?B?w6E=?=ahajkova
2022-12-15 15:57 ` Bruno Larsen
2022-12-15 16:35 ` Simon Marchi
[not found] ` <CAJVr-EOShPVS_ZBvfHqKkbPK1O3d+92DDbpEoeBVr1_s7_XWYA@mail.gmail.com>
2022-12-19 12:28 ` Alexandra Petlanova Hajkova [this message]
2022-12-19 13:04 ` Frank Ch. Eigler
2022-12-19 14:43 ` Andrew Burgess
2022-12-20 2:29 ` Simon Marchi
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=CAJVr-EP5T21eKcZ8vd0ka5kruL-qTB21L_PXnwpy9EbuSnW3pg@mail.gmail.com \
--to=ahajkova@redhat.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).