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

feature request: Clarify use of experimental api, to dump tracebacks #562

Closed
kristjanvalur opened this issue Jun 25, 2021 · 1 comment
Closed

Comments

@kristjanvalur
Copy link

The sentry api has an "experimental" part. I am interested in the ability to manually emit a traceback at the time of a crash, for example, during the before_send callback.
I can see the apis like sentry_unwind_stack_from_ucontext() but this is undocumented. Also sentry.h does not apparently ever provide one with a sentry_ucontext_t * to use. Additionally, the void **stacktrace_out, size_t max_len arguments are not explained (who owns memory, what does it contain, etc)

@Swatinem
Copy link
Member

I tried to expand on the docs a bit in #564. Currently, only unwinding from the current frame (sentry_unwind_stack(NULL, x, y)) is supported across all platforms. The caller has to allocate (probably on the stack) the instruction pointers.

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