Increase GDB Server init timeout #1129
Closed
Conversation
This file contains hidden or 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
|
Justification? |
|
I was just writting the issue to reference it :) |
|
Instead of just hanging for a very long time with no feedback, every 5 seconds you will get a message saying we are stil waiting. The overall timeout is not 60 seconds |
|
This means you have solved the cortex-debug timeout issue with another approach @haneefdm ? |
|
Yes. You should see my changes merged after the weekend. The real timeout now is 60 seconds. but with print statements to indicate that we are still waiting. You can test it yourselves once I merge |
|
Great, thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Increasing timeout value for GDB Server connection from 10s to 30s.
Fixes Issue:
#1130