-
Notifications
You must be signed in to change notification settings - Fork 7.9k
fix segfault in ZEND_FUNC_GET_ARGS
#12768
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
fix segfault in ZEND_FUNC_GET_ARGS
#12768
Conversation
In case a `ZEND_BIND_STATIC` is being executed, while the current chunk is full, the `zend_array_dup()` call will trigger a OOM in ZendMM which will crash, as the opline might be a dangling pointer.
In case a `ZEND_FUNC_GET_ARGS` is being executed, while the current chunk is full, the `zend_new_array()` call will trigger a OOM in ZendMM which will crash, as the opline might be a dangling pointer.
1cf0bcb
to
8a73bb5
Compare
This approach doesn't seem to work for |
@iluuu1994 can we explicitly set USE_ZEND_ALLOC=1 in the test via --ENV--? |
@bwoebi That should probably work. |
Yes, I too think that this should work. Is it okay if I have a look on Monday? |
This PR is based on the work of #12758 (which should be merged before this one, as it contains all the work on
zend_test
)In case a
ZEND_FUNC_GET_ARGS
is being executed, while the current chunk is full, thezend_new_array()
call will trigger a OOM in ZendMM which will crash, as the opline might be a dangling pointer.Commit 8a73bb5 brings the test and the fix