GDB advises that I enable a local debug repository. Should this be manually reverted after the trace has been generated?

When I invoked gdb via KDE’s Crashed Processes Viewer to generate a bt of a crash by an .AppImage file, it stated:

Missing separate debuginfo for the main executable file.
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/2c/d6d9e84e87bcb6de1d1e90d695b064e6b7368f

Missing debuginfo packages are common, and usually remdiated by a dnf install. However, it appears to be advising that I permanently enable a local repository merely for this purpose.

Is my estimate correct? If so, should I manually remove it afterward?

Oh. Doesn’t appear to matter:

PS /home/RokeJulianLockhart> sudo dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/2c/d6d9e84e87bcb6de1d1e90d695b064e6b7368f
[sudo] password for RokeJulianLockhart: 
Updating and loading repositories:
Repositories loaded.
Failed to resolve the transaction:
No match for argument: /usr/lib/debug/.build-id/2c/d6d9e84e87bcb6de1d1e90d695b064e6b7368f
You can try to add to command line:
  --skip-unavailable to skip unavailable packages

This enables the repos only for this command, its not persistant.
So there is nothing left enabled. But you might want to remove the debuginfo packages that were installed.

@barryascott, do you mean that debuginfo -y installs .RPMs too? I was under the impression that what it downloaded was ephemeral.

You can check for installed debuginfo RPMs using the command rpm -qa | grep debuginfo.

As you used a dnf install command it will have installed a debuginfo RPM for you.

1 Like

@barryascott, I don’t see any which should correspond to the command, weirdly:

  1. #!/usr/bin/env -S bash
    rpm -qa | grep -e 'debuginfo'
    
  2. PS /home/RokeJulianLockhart> rpm -qa | grep debuginfo
    x264-debuginfo-0.164-13.20231001git31e19f92.fc40.x86_64
    x264-libs-debuginfo-0.164-13.20231001git31e19f92.fc40.x86_64
    x265-debuginfo-3.6-2.fc40.x86_64
    x265-libs-debuginfo-3.6-2.fc40.x86_64
    plasma-systemsettings-debuginfo-6.2.3-1.fc41.x86_64
    dolphin-debuginfo-24.08.3-1.fc41.x86_64
    elfutils-debuginfod-client-0.192-6.fc41.x86_64
    elfutils-debuginfod-client-0.192-6.fc41.i686
    

Usually, it requests that I install a *.-debuginfo package from the existing repositories, rather than a hash path, so perhaps it just doesn’t cope with traces for .AppImages?

I do not use app image and don’t know, sorry.

1 Like

For AppImages you can use the application"Gear Lever"
This App is storing the images in /home/$USERNAME/AppImages. Just as a hint to find unused apps.

@ilikelinux, that’s what I use:

Does that impact the GDB’s ability to acquire a trace?