Update mini-gdbstub for the on_interrupt feature #115
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm glad to introduce the new feature on the
mini-gdbstub
library. With this update, we can receive the interrupt from the GDB client, thus breaking the original flow of the emulator if needed. When the emulator runs in thecont
method, it will have a chance to receive an interrupt. Once received, theon_interrupt
method will be executed concurrently, which set theis_interrupt
to force to break the loop of thecont
method.It's a very useful feature to debug your emulator when it hangs in an unexpected infinite loop without stopping. With the help of GDB and debug information, you can interrupt the emulator and force it to stop, then look at which line of code it is stuck on or the status of the emulator(e.g. register, memory).