Skip to content
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

Closed
crass opened this issue Sep 24, 2021 · 6 comments
Closed

No org.claws_mail.Claws-Mail.Debug to install debugging symbols #19

crass opened this issue Sep 24, 2021 · 6 comments
Assignees

Comments

@crass
Copy link

crass commented Sep 24, 2021

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.

@cobratbq cobratbq self-assigned this Sep 24, 2021
@cobratbq
Copy link
Collaborator

I will look into debugging symbols. I need to figure out how to package those.

@cobratbq
Copy link
Collaborator

Okay, I discovered an inconsistency. Please try installing debug symbols through package org.claws_mail.Claws_Mail.Debug. Although you might still be missing some debug symbols, though maybe not an issue for your case.

I am not sure why the naming is inconsistent. Check flatpak remote-info -m flathub org.claws_mail.Claws-Mail to view for yourself which extensions there are and what names they have.

@cobratbq
Copy link
Collaborator

@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 3.18.0, of course.

@crass
Copy link
Author

crass commented Sep 26, 2021

I've been able to install the debug symbols as you've suggested by changing Claws-Mail to Claws_Mail from the main flathub repository.

@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 3.18.0, of course.

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.

@cobratbq
Copy link
Collaborator

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?

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'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.

I think the solution is two-fold:

  1. Enabling debugging #20 removes the /lib/debug path from clean-up instructions. That should preserve a lot more debug symbols. I just found out how flatpak handles debugging (extensions), so fixing this in the build instructions now.
  2. According to this documentation on flatpak it might be helpful to install the SDK (org.freedesktop.Sdk/x86_64/20.08, but can also be discovered through flatpak info -m org.claws_mail.Claws-Mail)

As for the specific issue: I suspect (but have not confirmed yet) that recent commits in libetpan are causing this.

@crass thanks for your effort. You've pointed me in the right direction on a couple of things.

@cobratbq
Copy link
Collaborator

Closing this as this should be fixed with #23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants