-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No org.claws_mail.Claws-Mail.Debug to install debugging symbols #19
Comments
I will look into debugging symbols. I need to figure out how to package those. |
Okay, I discovered an inconsistency. Please try installing debug symbols through package I am not sure why the naming is inconsistent. Check |
@crass the test build in comment #20 (comment) allows you to install a package with the additional debug symbols. This is assuming that your issues persist with package |
I've been able to install the debug symbols as you've suggested by changing
I'm confused by this comment because I didn't need to install from the testing repository. Maybe because I waited sufficiently long enough for it to be rolled out to the main repo? I've also noticed that it seems that this only includes debug symbols for the Claws-Mail binary, but not any of the libraries it uses. For instance, libetpan has no debug symbols. And another issue that I haven't figured out yet (which is more of a flatpak general issue) is how to get debugging symbols for libc. |
That confusion is my bad: I did not update the version of the flatpak-package with the upgrade to Claws-Mail 3.18.0. The last update (the broken one, and also the most recent one) were Claws-Mail 3.18.0 with flatpak-package saying 3.17.8. I still need to fix that.
I think the solution is two-fold:
As for the specific issue: I suspect (but have not confirmed yet) that recent commits in @crass thanks for your effort. You've pointed me in the right direction on a couple of things. |
Closing this as this should be fixed with #23. |
In trying to debug #18 I noticed that there's no debug symbols package, which could give better gdb backtraces and help with debugging crashes.
The text was updated successfully, but these errors were encountered: