Open mickyaero opened 7 years ago
Seems like the seg-fault in in moose.Table
. Sometimes it runs. This kind of bugs are hard to debug.
My guess is that moose.Table
needs to check that object exists before reading the value. Some thread might exist before moose.Table
reads them at the end; and all a Table left with an object which may be garbage collected (seg-fault); if not then execution is successfull. Just a guess.
Reproducible with clang++
compiler and python3
as well.
The value of currentStep_ is being updated just once. When the test_ksolve.py is run, it gives segmentation faults and sometimes correct answer(repeated answers). The branch is ksolve_openmp