Several network code related fixes (four for one special!) #9216
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.
Motivation / Problem
TCPConnecter
dtor was making illegal writes/reads when killed before resolving was doneBoth required fixing. And I had 2 code cleanups in my queue .. might as well add them.
Description
TCPConnecter
dtor was a bit evil, as two problems intersected:connection_string
was already free'd before the dtor ofTCPConnecter
was called. This was not expected. But because private/public wasn't set correctly for it,TCPQueryConnecter
was already freeing the memory in his ctor. This was unintentional.TCPConnecter
didn't join the resolve thread, so it could still be pending, and reading/writing information. Now instead, wait till the resolve thread finishes before destroyingTCPConnecter
.NetworkTCPQueryServer
disconnected the network. No clue why .. most likely once that sounded like a good idea, but it is totally unneeded now.Limitations
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.