Threads to kill hung program; fixed source display issue #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 added threads for sending and getting key input from the user. A mutex ensures that a kill, quit, esc command can be sent to restart the debugger when a debugged program hangs, e.g. in an infinite loop, and not interfere with the select_window() or form input.
There were certain situations where the source file window would display a random file, when it should be displaying the main source file, e.g. when setting a breakpoint while the program is not running and when killing the program. I added a separate buffer for the main source file and some logic to prevent this.
I changed the register window from wrapped to non-wrapped text. I also moved
create_scroll_buffer_llist()back intodisplay_lines.c.