I haven't been able to reproduce this locally, and I have no idea what exactly is going there.

it is failing randomly

sapi/phpdbg/tests/watch_001.phpt - sapi/phpdbg/tests/watch_004.phpt tests have never failed for me
but sapi/phpdbg/tests/watch_005.phpt - sapi/phpdbg/tests/watch_006.phpt is failing consistently with the same Termsig=-1073741819 error code, not sure if this is related, but can you reproduce the segfault for these tests on Windows 32-bit?

it is failing randomly

Yeah, I know, but I ran several times (x86 ZTS, with and without JIT), and it never failed. :(

Neither sapi/phpdbg/tests/watch_005.phpt nor sapi/phpdbg/tests/watch_006.phpt is failing for me. However, -1073741819 is basically 0xc0000005 which is the code for an access violation (aka. segfault), and these tests mention "intentionally causes segfaults"; these should be caught, though, but for some reason they're not (or an uncaught segfault happens). Anyway, hard to debug if not reproducible.

I do not know how to debug this, but here is repro code: https://github.com/mvorisek/php-src/tree/repro_win32bit_segfault

the sapi/phpdbg/tests/watch_005.phpt and sapi/phpdbg/tests/watch_006.phpt tests always fail [1], the env is Microsoft Windows Server 2019 Datacenter 64 bit OS & php-src compiled for x86 platform

is it possible to update the repro code to dump the C stack trace to understand the issue just from the CI output?

[1] https://github.com/mvorisek/php-src/runs/6213041816?check_suite_focus=true#step:5:84

is it possible to update the repro code to dump the C stack trace to understand the issue just from the CI output?

Hmm, that would require to install and register a post mortem debugger, which than would create a (huge) dump file. That dump file would need to be uploaded as artifact, and could then be downloaded for inspection. Not sure if that's worth the trouble for phpdbg issues.

duplicate of #9650