-
Notifications
You must be signed in to change notification settings - Fork 8k
Zend: handle IS_REFERENCE in _zendi_try_convert_scalar_to_number() #20876
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
Conversation
is your PR actually fixing this particular issue or is it the wrong one ? completely unrelated. (削除) Beside I m not even sure the change is correct (or needed more precisely) actually, looking at the bigger picture. (削除ここまで) nevermind, the issue is actually #20873 but then your change, while passing the assertion, now gives a zendmm leak.
arshidkv12
commented
Jan 9, 2026
Sorry.. it is #20873. I will check the memory leak.
f2a51d9 to
282bdb6
Compare
Also fixes #20875.
ndossche
commented
Jan 9, 2026
This looks wrong, I don't understand the trick with Z_EXTRA, and I believe handling references in _zendi_try_convert_scalar_to_number is wrong. Note that the root cause of the issue is that a reference ends up in a TMP, which is not allowed.
iluuu1994
commented
Jan 9, 2026
Probably also related to GH-20854, looks very similar.
Thank you. Please check the new commit: 842a996.
Uh oh!
There was an error while loading. Please reload this page.
_zendi_try_convert_scalar_to_number()did not explicitly handleIS_REFERENCE operands, which could result in hitting the EMPTY_SWITCH_DEFAULT_CASE()` assertion when references reached the function.#20873