summaryrefslogtreecommitdiff
path: root/azure/i386
diff options
context:
space:
mode:
authorNikita Popov <nikita.ppv@gmail.com>2020-06-12 14:57:08 +0200
committerNikita Popov <nikita.ppv@gmail.com>2020-06-12 15:02:12 +0200
commit50c87e92fc22ae3da5dda6f7340d3b786c6117a4 (patch)
treec8a824183dc116d58c73448e990dbab6daed01a4 /azure/i386
parentb7a55aaff272f28fc03e68b756ad2f232515aaf2 (diff)
downloadphp-git-50c87e92fc22ae3da5dda6f7340d3b786c6117a4.tar.gz
Use GC stack in nested data removal
We should be doing this anyway to prevent stack overflow, but on master this is important for an additional reason: The temporary GC buffer provided for get_gc handlers may get reused if the scan is performed recursively instead of indirected via the GC stack. This fixes oss-fuzz #23350.
Diffstat (limited to 'azure/i386')
0 files changed, 0 insertions, 0 deletions