You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been running sanity.functional locally (in containers in a fyre VM, anyway) and have been getting a segfault in cmdLineTester_pltest_0. I believe this is because the subtest j9vmem__testOverlappingSegments is unable to allocate any memory at all:
The problem was actually a little worse - if the test failed in the very first cycle, the cleanup procedure would attempt to deallocate every segment j from 1 to CYCLES - 1, because keepCycles[j] would always be zero. The same erroneous freeing would happen for segment 0 only if the initial memory allocation failed, like I said above.
The test cmdLineTester_pltest_0 still fails in various other ways for me, presumably because I'm running in containers (or I've set up the tests incorrectly), but #19517 does fix this particular issue.
I have been running
sanity.functional
locally (in containers in a fyre VM, anyway) and have been getting a segfault incmdLineTester_pltest_0
. I believe this is because the subtestj9vmem__testOverlappingSegments
is unable to allocate any memory at all:The backtrace I get is this:
(My debug information seems to be messed up a little - sorry).
I think the failure is happening here:
openj9/runtime/tests/port/j9vmemTest.c
Lines 3458 to 3468 in a56cbdf
and what's happening is:
i == 0
).keepCycles[0] >= 0
becausekeepCycles
was memset to 0 earlier in the functioncategory
of the memory is NULL.The text was updated successfully, but these errors were encountered: