Skip to content

Random segmentation fault when a panic is called in a tide request handler. #188

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

Closed
qdequele opened this issue Apr 2, 2020 · 1 comment

Comments

@qdequele
Copy link

qdequele commented Apr 2, 2020

I had a segmentation fault when I tried to add Sentry to my project. https://github.com/meilisearch/meilisearch

I have noticed that the segmentation fault appears when I call a panic! into one of my tide request handler.

To simplify the debug, I have created a new repository to create a minimal reproducible project. https://github.com/qdequele/test-sentry I also add an lldb backtrace file, but I explain in the readme all the step to reproduce the segmentation fault.

Apparently, it's from using the backtrace library. I'll let you be the judge of that, but if I can help, I'd be happy to.

@Swatinem
Copy link
Member

Now that backtrace is using gimli by default, I think we can close this?

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