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.

Sign up for GitHub

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

Jump to bottom

fail() backtrace #1315

Open
alex-s168 opened this issue Mar 5, 2025 · 1 comment
Open

fail() backtrace #1315

alex-s168 opened this issue Mar 5, 2025 · 1 comment

Comments

@alex-s168
Copy link
Contributor

use the target's backtrace functionality and then LM demangle the symbol names for helpful backtraces in fail()

there are two options I see for doing this:

  1. get C backtrace working on all targets: glibc, musl, and win32
  2. only support backtrace on glibc, and also define backtrace_symbols as weak declaration that does nothing.
@andrew-johnson-4
Copy link
Owner

Hmm, this sounds like a debugging feature. I sort of want it default "off" too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alex-s168 @andrew-johnson-4