CoreCLR PAL tests on QNX: Crashes and exceptions not reported as FAILED

[guesshe]

Trying to port coreclr to QNX platform and during pal test suite execution, crashes and exceptions are not reported as FAILED status. The overall test cases are still PASSED but hello_world.dll can' be launched. Following are the crashes and exceptions encountered.

• Process 329478169 (paltest_fprintf_test2) terminated SIGSEGV code=1 fltno=11 ip=0000000100078e10(/usr/lib/ldqnx-64.so.2@strlen+0x0000000000000000) mapaddr=0000000000078e10. ref=0000000000000000 Memory fault (core dumped)
• Process 335843353 (paltest_printf_test2) terminated SIGSEGV code=1 fltno=11 ip=0000000100078e10(/usr/lib/ldqnx-64.so.2@strlen+0x0000000000000000) mapaddr=0000000000078e10. ref=0000000000000000 Memory fault (core dumped)
• Process 346595353 (paltest_vfprintf_test2) terminated SIGSEGV code=1 fltno=11 ip=0000000100078e10(/usr/lib/ldqnx-64.so.2@strlen+0x0000000000000000) mapaddr=0000000000078e10. ref=0000000000000000 Memory fault (core dumped)

...'paltest_namedmutex_test1' failed at line 397. Expression: m != nullptr
'paltest_namedmutex_test1' failed at line 463. Expression: m2 != nullptr
'paltest_namedmutex_test1' failed at line 556. Expression: m != nullptr
'paltest_namedmutex_test1' failed at line 670. Expression: m != nullptr
'paltest_namedmutex_test1' failed at line 287. Expression: parentEvents[i] != nullptr
'paltest_namedmutex_test1' failed at line 695. Expression: InitializeParent(testName, parentEvents, childEvents)
'paltest_namedmutex_test1' failed at line 930. Expression: AbandonTests_Parent()
'paltest_namedmutex_test1' failed at line 273. Expression: WaitForSingleObject(childRunningEvent, FailTimeoutMilliseconds) == WAIT_OBJECT_0
'paltest_namedmutex_test1' failed at line 320. Expression: AcquireChildRunningEvent(testName, childRunningEvent)
'paltest_namedmutex_test1' failed at line 759. Expression: InitializeChild(testName, childRunningEvent, parentEvents, childEvents)
........ReleaseMutex() test returned 0.

Here is the final output
Finished running PAL tests.

PAL Test Results:
Passed: 726
Failed: 0

[ghost]

Tagging subscribers to this area: @ViktorHofer
Notify danmosemsft if you want to be subscribed.

[janvorli]

I'll take a look to see whether that is something specific to the QNX port or if we've regressed there.

[janvorli]

It seems this problem is specific to QNX somehow. I've tried to induce a SIGSEGV into the paltest_fprintf_test2 and the test was reported as failed.

.
.
.
FAILED: c_runtime/printf/test2/paltest_printf_test2. Exit code: 139
.
.
.
PAL Test Results:
  Passed: 715
  Failed: 1

[janvorli]

The failure is determined based on the exit code that we extract like this after the test completion or crash:

TEST_EXIT_CODE=$?

I wonder if it is possible that on QNX, SIGSEGV and similar failures are not projected into the exit code. You can try to echo the TEST_EXIT_CODE to console after each test here:

runtime/src/coreclr/src/pal/tests/palsuite/runpaltests.sh

Line 133 in 2d1f7b0

to see.

[guesshe]

@janvorli Thanks! I will take a look at from QNX's side.

[guesshe]

@janvorli How about these exceptions?

[janvorli]

@guesshe regarding the SIGSEGVs, I cannot really give you any hints until you have stack trace at the exception.

[dotnet-policy-service]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.