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

[merp] Fix return value handling of posix_spawn #10823

Merged
merged 1 commit into from
Sep 28, 2018

Conversation

alexanderkyte
Copy link
Contributor

@slluis requested this change be merged by tomorrow to make a release window

// // FIXME error handling
if (status == 0)
g_error ("Could not start merp\n");
g_assertf (status == 0, "Could not start merp\n");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

g_assertf (status == 0, "Could not start merp (%d)\n", status);?
g_assertf (status == 0, "posix_spawn(/usr/bin/open %s) failed with status:%d\n", config.merpGUIPath, status);?

Granted, if things are bad, formating of the assert message is risky; it requires heap. The way to handle that is do allocations/formats in startup, leaving as little work as possible for the error path. And heap-free putting in the status.

@alexanderkyte
Copy link
Contributor Author

It seems the 2018-02 backport was merged. I'm not going to revert that. I will close and update my updated error formatting to the 2018-04 and 2018-06 PRs.

@alexanderkyte
Copy link
Contributor Author

@monojenkins backport 2018-06

@alexanderkyte
Copy link
Contributor Author

@monojenkins backport 2018-04

@alexanderkyte
Copy link
Contributor Author

@monojenkins build failed

akoeplinger added a commit that referenced this pull request Sep 27, 2018
It was missing the format arguments that were in a later iteration of #10823
@marek-safar
Copy link
Member

@monojenkins backport 2018-08

@luhenry luhenry merged commit a7d355d into mono:master Sep 28, 2018
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants