procdump on Cpp Windows CI

[alinaliBQ]

Hi, does anyone know how to get procdump to produce a detailed log for segFault when running the cpp_test.sh?

For context, I am trying to get procdump logs on the AMD64 Windows MinGW CLANG64 C++ and AMD64 Windows MinGW MINGW64 C++ workflows. The Test step code is inside cpp.yml. The segFault error that I am seeing is only reproducible on the CI and not on my local environment.

[kou]

This may work...

diff --git a/cpp/cmake_modules/BuildUtils.cmake b/cpp/cmake_modules/BuildUtils.cmake
index 134f47b12e..f198fddc0b 100644
--- a/cpp/cmake_modules/BuildUtils.cmake
+++ b/cpp/cmake_modules/BuildUtils.cmake
@@ -736,7 +736,7 @@ function(ADD_TEST_CASE REL_TEST_NAME)
                valgrind --suppressions=valgrind.supp --tool=memcheck --gen-suppressions=all \
                  --num-callers=500 --leak-check=full --leak-check-heuristics=stdstring \
                  --error-exitcode=1 ${TEST_PATH} ${ARG_TEST_ARGUMENTS}")
-  elseif(WIN32 OR CMAKE_SYSTEM_NAME STREQUAL "Emscripten")
+  elseif(MSVC OR CMAKE_SYSTEM_NAME STREQUAL "Emscripten")
     add_test(NAME ${TEST_NAME} COMMAND ${TEST_NAME} ${ARG_TEST_ARGUMENTS})
   else()
     add_test(${TEST_NAME}

[alinaliBQ]

Hi @kou, I have tried out the solution, unfortunately it give me the inappropriate file type or format error (link to the run)

Test project D:/a/arrow/arrow/build/cpp
      Start  1: arrow-array-test
Process not started
 D:/a/arrow/arrow/cpp/build-support/run-test.sh
[inappropriate file type or format]

[kou]

Ah, the command is executed in non MSYS2 environment. This may work:

diff --git a/cpp/cmake_modules/BuildUtils.cmake b/cpp/cmake_modules/BuildUtils.cmake
index 134f47b12e..3494d9f87f 100644
--- a/cpp/cmake_modules/BuildUtils.cmake
+++ b/cpp/cmake_modules/BuildUtils.cmake
@@ -736,11 +736,11 @@ function(ADD_TEST_CASE REL_TEST_NAME)
                valgrind --suppressions=valgrind.supp --tool=memcheck --gen-suppressions=all \
                  --num-callers=500 --leak-check=full --leak-check-heuristics=stdstring \
                  --error-exitcode=1 ${TEST_PATH} ${ARG_TEST_ARGUMENTS}")
-  elseif(WIN32 OR CMAKE_SYSTEM_NAME STREQUAL "Emscripten")
+  elseif(MSVC OR CMAKE_SYSTEM_NAME STREQUAL "Emscripten")
     add_test(NAME ${TEST_NAME} COMMAND ${TEST_NAME} ${ARG_TEST_ARGUMENTS})
   else()
     add_test(${TEST_NAME}
-             ${BUILD_SUPPORT_DIR}/run-test.sh
+             /usr/bin/env bash ${BUILD_SUPPORT_DIR}/run-test.sh
              ${CMAKE_BINARY_DIR}
              test
              ${TEST_PATH}

[alinaliBQ]

Hi Thanks! I have tried it, the command worked for me after removing /usr/bin/env because GitHub had error Could not find executable /usr/bin/env. Eventually I got the same output as before, it shows the test cases run, but it doesn't show any coredump or where the segmentation fault occurred (link to log). I think the segmentation fault occurs after all tests are passed.

Running arrow-flight-sql-odbc-test, redirecting output into D:/a/arrow/arrow/build/cpp/build/test-logs/arrow-flight-sql-odbc-test.txt (attempt 1/1)
D:/a/arrow/arrow/cpp/build-support/run-test.sh: line 87:  4184 Segmentation fault      $TEST_EXECUTABLE "$@" > $LOGFILE.raw 2>&1
[==========] Running 111 tests from 12 test suites.
[----------] Global test environment set-up.
[----------] 46 tests from FlightSQLODBCTestBase/0, where TypeParam = arrow::flight::sql::odbc::FlightSQLODBCMockTestBase
[ RUN      ] FlightSQLODBCTestBase/0.TestSQLSetConnectAttrAsyncDbcEventUnsupported
...

[kou]

You're right. /usr/bin/env is needless. Sorry.

Hmm. It seems that core files aren't generated on Windows... Sorry.

We may need to enable user-mode dumps: https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps

[alinaliBQ]

It's ok, thank you for looking into this. I have tried setting the key on CI but it is not producing any coredumps still and the crash dump log folder is empty. (Link to log)