fix nil pointer exception when calling Start again after address binding error #2131
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.
There is a nil pointer exception because the code assigns a nil value to an interface (
e.Listener
) which ends up creating a non-nil interface containing a nil pointer. Using this will result in the nil pointer exception and checking thee.Listener
againstnil
will befalse
-- which is why the Listener is not recreated and overwritten the during the second call toStart
.Small code example that triggers this error (given an existing echo router):