Fedora Atomic (Silverblue) debugging with gdb - "No symbol table info available." "Missing file(s), try: dnf --enablerepo='*debug*' install..."

Hi, hoping someone out there can help me with this. I’m trying to generate a stack trace for a crash that’s occurring with the Fedora flatpak of GNOME Calendar. I am on Fedora Silverblue 43.20260221.0, kernel 6.18.12-200.fc43.x86_64, GNOME 49.

The problem is, after installing gdb (which I had to install via rpm-ostree), then following the GNOME handbook to produce a stack trace (Stack Traces - GNOME Project Handbook), I get the following issues:

Missing file(s), try: dnf --enablerepo=‘debug’ install /usr/lib/.build-id/b2/fe50fe5018ba27ffcc0d0ba6c5a3964de550d3 /usr/lib/debug/.build-id/b2/fe50fe5018ba27ffcc0d0ba6c5a3964de550d3.debug

#0 0x00007f541a70313b in ?? ()
No symbol table info available.

What’s above is just snippets from the output. There are many lines of this which look basically the same.

Does anyone know how I can generate a proper stack trace for GNOME Calendar on Fedora Silverblue? Thank you so much.

You probably need to follow the instructions for getting stack traces for Flatpak apps, available in the same document but further down the page.

It would also be good to test the Flathub version of GNOME Calendar separately, in order to check if it’s an upstream issue or not.

Ahhh thank you so much! I forgot the command is different for flatpaks.

By the way, do you know how I can submit changes to the handbook? The first time I followed that guide, I had a hell of a time figuring out that (gdb) bt full was not meant to fully copy/pasted as a command. I’ve been on Linux for about a year now, and stuff like this is not obvious to newcomers. I’d like to update the handbook so that it’s a bit easier for noobs like me to generate stack traces as needed.

1 Like
2 Likes

You’re welcome!

I would suggest to start with reporting your proposals as Requests for Enhancement (RFE) in the Handbook’s issue tracker.

1 Like

Thank you!!!

1 Like