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
Reported by: Rolf Ade <rolf <at> pointsman.de>
Date: Sat, 4 May 2024 02:02:01 UTC
Severity: normal
Found in version 29.1
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #32 received at 70764 <at> debbugs.gnu.org (full text, mbox):
Am 04.05.24 um 18:12 schrieb Eli Zaretskii:
>> Date: Sat, 4 May 2024 17:42:20 +0200
>> Cc: 70764 <at> debbugs.gnu.org
>> From: Rolf Ade <rolf <at> pointsman.de>
>>
>> Am 04.05.24 um 16:11 schrieb Eli Zaretskii:
>>>> Date: Sat, 4 May 2024 15:32:27 +0200
>>>> From: Rolf Ade <rolf <at> pointsman.de>
[...]
>>>
>>> Strange. GDB 10.1 was the version where debuginfod support was added.
>>> What does the shell command below show?
>>>
>>> $ gdb --config | fgrep debuginfod
>>
>> This returns
>>
>> --with-debuginfod
>
> Then I'm really stumped.
>
> If you start GDB from the shell prompt, like this:
>
> $ gdb ./emacs
>
> and then, when GDB shows its "(gdb)" prompt, type
>
> (gdb) set debuginfod enabled on
>
> do you also see that "No symbol" error message?
Yes:
(gdb) set debuginfod enabled on
No symbol "debuginfod" in current context.
(gdb)
> And also please try this:
>
> $ gdb -i=mi ./emacs
> ...
> -gdb-set debuginfod enabled on
>
> and see if you get any error message that way.
Yes:
(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). I see this on
two different boxes with debian 11.9; this is not specific to a single machine.
But Bullseye still isn't that uncommon; so others should also see this, I suppose?
This bug report was last modified 1 year and 60 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.