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

Message #40 received at 70764-done <at> debbugs.gnu.org (full text, mbox):

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.