#188 Fedora flatpaks should be debuggable
Closed: Fixed 2 days ago by catanzaro. Opened a year ago by catanzaro.

Fedora flatpaks should be debuggable, somehow. That is, it should be possible to generate a useful backtrace for a crash that shows stack frames, member variables, etc. Ideally, the 'flatpak-coredumpctl' command would work as it does for other flatpaks, though that might not be possible depending on the implementation details. Owen has been looking into using gdbserver.


Owen, any updates on this topic? I understand debuginfod is now present in Fedora, so in theory we should not need to create .Debug extensions for our flatpaks provided debuginfod is working nicely inside our flatpaks...?

debuginfod is available as a package in Fedora, but there's no debuginfod server serving debuginfo for Fedora packages. It's not a hard job to have that at - least for the packages in current - Fedora Flatpaks, but I don't know when we could get it prioritized and done in Fedora infrastructure.

debuginfod is available as a package in Fedora, but there's no debuginfod server serving debuginfo for Fedora packages. It's not a hard job to have that at - least for the packages in current - Fedora Flatpaks, but I don't know when we could get it prioritized and done in Fedora infrastructure.

I just tested this and debuginfo for Fedora flatpaks is working out-of-the-box in Fedora 35 via debuginfod. I'm surprised it works, but it does. There is nothing more to do. Closing.

Metadata Update from @catanzaro:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 days ago

Login to comment on this ticket.

Metadata