From: Eli Zaretskii <eliz@gnu.org>
To: rolf@pointsman.de
Cc: 70764-done@debbugs.gnu.org
Subject: bug#70764: 29.1; M-x gdb: don't ask me about debuginfod server if debuginfod is not in context
Date: Sat, 18 May 2024 11:36:21 +0300 [thread overview]
Message-ID: <86y187ecu2.fsf@gnu.org> (raw)
In-Reply-To: <86a5l5fquk.fsf@gnu.org> (message from Eli Zaretskii on Sat, 04 May 2024 20:07:31 +0300)
> Cc: 70764@debbugs.gnu.org
> Date: Sat, 04 May 2024 20:07:31 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> > (gdb)
> > -gdb-set debuginfod enabled on
> > ^error,msg="No symbol \"debuginfod\" in current context."
> > (gdb)
> >
> > So, this all seems to lead to that the gdb shipped with Bullseye isn't correctly
> > build (despite the --with-debuginfod in the gdb --config output).
>
> Most probably, yes.
>
> > But Bullseye still isn't that uncommon; so others should also see this, I suppose?
>
> Unfortunately, the only better alternative to stop these error
> messages is for you to customize gdb-debuginfod-enable-setting to the
> nil value. That is the only way we know of that allows to prevent the
> error messages by avoiding to even try the problematic setting. No
> other way we tried at the time to dynamically detect the support
> worked in a satisfactory manner, basically because trying an
> unsupported command is bound to trigger some error message.
No further comments within 2 weeks, so I'm now closing this bug.
prev parent reply other threads:[~2024-05-18 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 2:00 bug#70764: 29.1; M-x gdb: don't ask me about debuginfod server if debuginfod is not in context Rolf Ade
2024-05-04 7:20 ` Eli Zaretskii
2024-05-04 13:32 ` Rolf Ade
2024-05-04 13:33 ` Rolf Ade
[not found] ` <54b3a581-8e00-4bf1-9051-5b826cd9c306@pointsman.de>
2024-05-04 14:11 ` Eli Zaretskii
2024-05-04 14:23 ` Eli Zaretskii
2024-05-04 15:54 ` Rolf Ade
2024-05-04 15:42 ` Rolf Ade
2024-05-04 16:12 ` Eli Zaretskii
2024-05-04 16:26 ` Rolf Ade
2024-05-04 17:07 ` Eli Zaretskii
2024-05-18 8:36 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y187ecu2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70764-done@debbugs.gnu.org \
--cc=rolf@pointsman.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).