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

Crash reporting from vere #659

Open
jalehman opened this issue Jun 12, 2024 · 0 comments
Open

Crash reporting from vere #659

jalehman opened this issue Jun 12, 2024 · 0 comments
Assignees
@ripperi

Comments

@jalehman
Copy link
Member

We currently have no quantitative measure for how stable Urbit is. Having the runtime submit a report of some kind to a server when it crashes, even if light on details, would allow us to begin measuring exactly how frequently crashes occur. It would be great to know what kind of crash occurred as well, but even knowing that a crash happened would be useful.

This is the kind of feature that should be opt-in, e.g. with a runtime flag. We could cover a large portion of the running Urbit fleet by working with hosting providers to turn this on.
@jalehman jalehman converted this from a draft issue Jun 12, 2024
@ripperi ripperi mentioned this issue Jul 11, 2024
Merged
pkova added a commit that referenced this issue Sep 16, 2024
@pkova
Add stacktrace (#674)
3761ed0 
Related to #659 

Adds backtrace printing to SIGSEGV signal handling. Tries to print file
and line number with libbacktrace, falls back to using standard
backtrace when debug info is unavailable.

Before:
<img width="715" alt="Screenshot 2024-07-11 at 15 58 52"
src="https://github.com/urbit/vere/assets/22086553/3ba89d96-c50c-40a5-8fd4-f6e636b8aec3">

After (with dsyms):
<img width="715" alt="Screenshot 2024-07-24 at 17 11 56"
src="https://github.com/user-attachments/assets/b333516f-c36f-48ce-afd2-95de9f812843">

After (without dsyms):
<img width="715" alt="Screenshot 2024-07-24 at 17 14 31"
src="https://github.com/user-attachments/assets/59956429-2fc7-478e-a05d-1807db21b18f">
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ripperi ripperi

Labels
None yet
Projects
Incremental Improvements
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jalehman @ripperi