Fix segfault on exception when RVO is used #1131
Merged
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.
Scenario:
If SomeClass::anotherMethod() throws an exception, phalcon_alt_call_method() will destroy its return_value (which is the same as SomeClass::someMethod()'s return_value) and set it to NULL. When SomeClass::someMethod() returns, EG(exception) will not be NULL and phalcon_alt_call_method() will try to destroy the already destroyed return_value and will crash.
Something like this:
This happened for this case:
This is a temporary fix as it only covers the case when the methods are called by Phalcon using its phalcon_call_XXX() functions. It does not cover the scenario when SomeClass::someMethod() is called from the userspace.