Add gdb-server persistence #132
Merged
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
…s loop" This reverts commit 1c2828c.
When started with -m, or connected with 'target extended-remote', the GDB server will not terminate upon disconnection from GDB, instead it will begin listening for conenctions again. Starting with extended-remote also has the advantage of allowing 'run' to be used to reset the target and begin again. Unfortunately, 'start' is not working properly, as it does not send a reset packet (R), so it complains when it tries to access memory before it is connected to the target.
This was
linked to
issues
Mar 21, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As noted in issue #131, st-util exits upon disconnect from GDB. This is expected behavior, but it is nice to have the option to keep st-util up. Commit 1c2828c attempted to add support for this, but failed, as the listening socket has already been closed where the commit tries to jump back to.
This pull request adds working support for persistence, either enabled with the option '-m', or by connecting to the server with 'target extended-remote'. In extended-remote mode, 'run' can be used to reset and continue the target. Unfortunately, 'start' is broken, as, for some reason, it tries to access memory before sending the reset packet.
This closes issue #131.