Skip to content

libbacktrace: update to latest to fix MacOS backtraces (Sequoia, 2024). #8421

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rustyrussell
Copy link
Contributor

Changelog-Fixed: logging: Fixed crash backtraces on macOS Sequoia.
Reported-by: @sangbida

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Fixed: logging: Fixed crash backtraces on macOS Sequoia.
Reported-by: @sangbida
@rustyrussell rustyrussell added this to the v25.09 milestone Jul 21, 2025
@sangbida
Copy link
Collaborator

sangbida commented Jul 22, 2025

This change didn't seem to resolve the libbacktrace: no debug info in Mach-O executable error for me. I think the debug symbols are strored differently to how it's stored on Linux. On Linux the debug symbols are stored directly into the binary where as on macOS debug symbols are stored separately from the binary.

So far I have:

  • Added -g to compile flags and removed it from link flags, so my .o files contain full DWARF
  • Rebuilt clean
  • Run dsymutil lightningd/lightning_hsmd and dsymutil tools/hsmtool and confirmed that
dwarfdump --debug-info lightningd/lightning_hsmd.dSYM/Contents/Resources/DWARF/lightning_hsmd

the debug info contains the compile-unit DIEs.

Despite this, libbacktrace still reports issues. Previously, the error was libbacktrace: no debug info in Mach-O executable after the changes above the error message has changed to libbacktrace: failed to read executable information. This is maybe a mild improvement from before?? because it seems like the debug info is there now but libbacktrace can't find it or understand it? It is also possible that libbacktrace may still be looking for the debug info in a different loacation.

I think I'm going to take a break on this today and look at it again tomorrow hopefully with better luck!

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

Successfully merging this pull request may close these issues.

2 participants