[ISSUE #52]Fix infinite loop on tcptransport connect #59
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
Member
|
Could you please review the PR #60 ? |
Contributor
Author
|
OK, I will have a look at it. |
ShannonDing
changed the title
Member
|
while polishing the PR #60, this PR will be merged first. |
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.
The execution order of these two steps below are uncertain:
If the thread runs first, the value of m_ReadDatathread will be NULL, the codes inside 'while (m_ReadDatathread) {}' will never be executed, then 'm_event_base_status' will never store 'true', so TcpTransport::connect will stay on the loop infintely.