Hi - > > If I read drkonqi sources correctly in that gdb is being used as the > > backtracing backend. That suggests that its automatic debuginfod-based > > downloading should be working on F35. Do you have a recipe for > > triggering this crash and the dr. konqi processing? > No good way [to reproduce]. After composing the above email, I > noticed it was lingering in the outbox. After some poking around, I > found that one of the mail agents was no longer on dbus. I can only > speculate it segfaulted. Bummer. > And because it says no debug information, I don't have any clue > where in kontact problems are happening. With debuginfod env vars set up, it shouldn't say that. It (gdb or similar) should just go ahead and download it. If that's not working in this context, I'd love to look closer why. > [...] > But if there is a new feature in F35 that make crashes meaningful again https://fedoraproject.org/wiki/Changes/DebuginfodByDefault should help - FChE _______________________________________________ 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
