GNU bug report logs - #70764
29.1; M-x gdb: don't ask me about debuginfod server if debuginfod is not in context

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#70764: closed (29.1; M-x gdb: don't ask me about debuginfod
 server if debuginfod is not in context)
Date: Sat, 18 May 2024 08:37:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 18 May 2024 11:36:21 +0300
with message-id <86y187ecu2.fsf <at> gnu.org>
and subject line Re: bug#70764: 29.1; M-x gdb: don't ask me about debuginfod server if debuginfod is not in context
has caused the debbugs.gnu.org bug report #70764,
regarding 29.1; M-x gdb: don't ask me about debuginfod server if debuginfod is not in context
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
70764: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=70764
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Rolf Ade <rolf <at> pointsman.de>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.1; M-x gdb: don't ask me about debuginfod server if debuginfod
 is not in context
Date: Sat, 04 May 2024 04:00:20 +0200

With 29.1 as well as with trunk(both tested with -Q) if I call M-x gdb I
get asked:

"Enable querying debuginfod servers for this session? (y or n)"

Even if I answer with "n" I get the message:

"No symbol \"debuginfod\" in current context."

This can't be right. Declining to use a feature should not be answered
with a message that it would not be available anyways (what the message
seem to tell me).

Digging around a bit it turns out there is a variable to customise the
behaviour here: gdb-debuginfod-enable-setting. Its default value is
'ask.

From a user perspective it only make sense to be ask about wanting
something if this something is avaliable.

If it is about the advertising aspect then why not more clear don't ask
questions and instead write a message like: "You cannot use debuginfod
servers. Consider using this marvelous feature".

rolf

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: rolf <at> pointsman.de
Cc: 70764-done <at> debbugs.gnu.org
Subject: Re: 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

> Cc: 70764 <at> debbugs.gnu.org
> Date: Sat, 04 May 2024 20:07:31 +0300
> From: Eli Zaretskii <eliz <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.