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

Launch GDB session on Fatal Error #21

Closed
daniel5151 opened this issue Apr 17, 2020 · 1 comment
Closed

Launch GDB session on Fatal Error #21

daniel5151 opened this issue Apr 17, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@daniel5151
Copy link
Owner

Instead of immediately bailing when a fatal error occurs, it would be nice to launch a GDB server which can be used to inspect the current CPU and Memory state at the time of the crash.

This should be an optional feature (i.e: toggled via a CLI flag), as bailing immediately leads to faster iteration times when developing new code (as opposed to debugging existing code).
@daniel5151 daniel5151 added the enhancement New feature or request label Apr 17, 2020
@daniel5151
Copy link
Owner Author

Closed as part of d4e9bcf.

As long as a GDB client is connected on startup, the session will transition into a post-mortem mode when a fatal error is encountered.

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

No branches or pull requests
1 participant
@daniel5151