On 5/18/22 23:57, Jerry James wrote:
On Wed, May 18, 2022 at 9:41 PM Jerry James <loganjerry@xxxxxxxxx> wrote:
I just updated my home machine to F36. Now, when I try to debug a
Fedora-built package after installing the appropriate debuginfo
packages with dnf, I get:
(No debugging symbols found in .gnu_debugdata for [path to ELF object])
for every library. Is debuginfod the only supported way to get usable
debuginfo now? I thought it was an optional convenience feature. I
would rather manage the debuginfo with dnf.
Some experimentation shows that there is some magic threshold at play
here. After I installed debuginfo for a bunch of libraries I am *not*
interested in, GDB started loading debuginfo for the one of interest.
So is there some kind of dependency between debuginfo packages that
must be satisfied before the debuginfo can be used? I never
encountered this on F35, so I'm not sure what the rules are now.
I think gdb starts loading debuginfo in background, and it takes a while
so you started seeing it after a delay.
I am not sure how to check the progress of this background retrieval; I
don't remember any messages even while in gdb
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
