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

Add core dumps #14

Open
dynafide opened this issue Nov 2, 2022 · 0 comments
Open

Add core dumps #14

dynafide opened this issue Nov 2, 2022 · 0 comments
Labels
enhancement New feature or request Resurgence Planned Feature Planned feature for Resurgence

Comments

@dynafide
Copy link
Collaborator

dynafide commented Nov 2, 2022

Add a crash / core dumps mechanism that can either be triggered manually or when faults occur. This will help with debugging both the Resurgence VM as well as programs running inside of it. Core dumps should contain the following:

  • a copy of the instructions and bytecode header re-encoded from the Codeholder
  • a list of the states of each recursive execute_instruction call, including the register values and the current instruction number they are at
  • a complete copy of all stack frames
  • a complete copy of the stack

This should be output in a portable binary format that can be used in other applications for debugging purposes.

@dynafide dynafide added enhancement New feature or request Resurgence Planned Feature Planned feature for Resurgence labels Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Resurgence Planned Feature Planned feature for Resurgence
Projects
None yet
Development

No branches or pull requests

1 participant