Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail pony_start if ASIO backend wasn't successfully initialized #2381

Merged
merged 1 commit into from
Nov 28, 2017

Conversation

dipinhora
Copy link
Contributor

Prior to this commit, the ASIO backend could fail initialization
but the runtime would continue to start up anyway resulting in
segfaults or assertion failures.

This commit changes things so that if the backend initialization
fails, the runtime exits immediately with an error.

This commit also fixes the asio restart logic from PR #2373 to
properly re-initialize the backend first.

Prior to this commit, the ASIO backend could fail initialization
but the runtime would continue to start up anyway resulting in
segfaults or assertion failures.

This commit changes things so that if the backend initialization
fails, the runtime exits immediately with an error.

This commit also fixes the asio restart logic from PR ponylang#2373 to
properly re-initialize the backend first.
@jemc jemc added the changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge label Nov 27, 2017
@SeanTAllen SeanTAllen merged commit 1468374 into ponylang:master Nov 28, 2017
ponylang-main added a commit that referenced this pull request Nov 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants