Crash with STATUS_ACCESS_VIOLATION in gio/max-version test on msys2-mingw32
See this job. All we get from the logs is this:
================================== 230/301 ===================================
test: glib:gio / max-version
start time: 14:03:52
duration: 0.09s
result: (exit status 3221225477 or signal 3221225349 SIGinvalid)
command: MALLOC_PERTURB_=145 G_ENABLE_DIAGNOSTIC=1 G_TEST_BUILDDIR=C:/_r/_builds/vJWzEqDv/0/pwithnall/glib/_build/
gio/tests PATH=C:/_r/_builds/vJWzEqDv/0/pwithnall/glib/_build/gmodule;C:/_r/_builds/vJWzEqDv/0/pwithnall/glib/_build/gi
o;C:/_r/_builds/vJWzEqDv/0/pwithnall/glib/_build/glib;C:/_r/_builds/vJWzEqDv/0/pwithnall/glib/_build/gobject;C:\Users\u
ser\.local\bin;C:\msys64\home\user\.local\bin;C:\msys64\MINGW32\bin;C:\msys64\mingw32\bin;C:\msys64\usr\local\bin;C:\ms
ys64\usr\bin;C:\msys64\usr\bin;C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPower
Shell\v1.0\;C:\msys64\usr\bin\site_perl;C:\msys64\usr\bin\vendor_perl;C:\msys64\usr\bin\core_perl;C:\msys64\MINGW32\bin
\ G_TEST_SRCDIR=C:/_r/_builds/vJWzEqDv/0/pwithnall/glib/gio/tests MALLOC_CHECK_=2 GIO_MODULE_DIR= G_DEBUG=gc-friendly C
:/_r/_builds/vJWzEqDv/0/pwithnall/glib/_build/gio/tests/max-version.exe
----------------------------------- stdout -----------------------------------
TAP version 13
# random seed: R02S797bdeded8994cc3ada80fbf79c7655a
1..1
# Start of max-version tests
# GLib-GIO-DEBUG: Loaded GCancellable from GIO library
ok 1 /max-version/tested-at-compile-time
# End of max-version tests
----------------------------------- stderr -----------------------------------
(test program exited with status code 3221225477)
==============================================================================
Status code 3221225477 is 0xC0000005 in base 16, which is STATUS_ACCESS_VIOLATION
. That indicates an out-of-bounds memory access.
Without a backtrace or coredump it’s impossible to debug this, but at least it’s recorded somewhere now. Perhaps someone with an msys2-mingw32 setup could repeatedly run the max-version
test and see if they can get it to fail?