ext/standard/tests: strings/wordwrap_memory_limit_32bit.phpt has two outputs

It turns out that on a 32-bit system, this test can produce either the
"usual" expected output from the 64-bit test, OR the 32-bit-only
integer overflow message. We copy the dual expected outputs from
chunk_split_variation1_32bit.phpt to handle both cases.

This fixes an earlier commit that split the two tests based only on
the size of an int (32-bit versus 64-bit). The CI reveals that, at
least on a debug/zts build, the "64-bit" memory limit error (and not
the integer overflow error) is still produced.
This commit is contained in:
Michael Orlitzky 2024-07-04 07:49:01 -04:00 committed by Niels Dossche
parent 68a0efedeb
commit 27dd393be9
No known key found for this signature in database
GPG Key ID: B8A8AD166DF0E2E5

View File

@ -16,4 +16,4 @@ wordwrap($str, 1, $str2);
?>
--EXPECTF--
Fatal error: Possible integer overflow in memory allocation (4294901777 + %d) in %s on line %d
Fatal error: %rAllowed memory size of %d bytes exhausted%s\(tried to allocate %d bytes\)|Possible integer overflow in memory allocation \(4294901777 \+ %d\)%r in %s on line %d