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've added two new tests that catch this error TEST_F(RoadRunnerAPITestsWithMCJit, getIdsAfterSetConservedMoiety) and TEST_F(RoadRunnerAPITestsWithLLJit, getIdsAfterSetConservedMoiety) but disabled them for the time being. Basically we get a heap buffer overflow error when we do:
RoadRunner rr(sbml);
rr.setConservedMoietyAnalysis(true); // does a regenerate model.
std::list<std::string> l;
rr.getIds(SelectionRecord::ALL, l);
These tests pass in Release and Debug builds but fail in when CMAKE_BUILD_TYPE="Asan" (which works out of the box on mac, provided sanitizers are installed - windows will be problematic). We may also be able to detect this with valgrind but I haven't tried.
I haven't been able to figure out what is going on here but I'm thinking that this is a symptom of the numbers of species changing after the regenerate model associated with the call to setConservedMoieties.
The text was updated successfully, but these errors were encountered:
…ing to RoadRunner::getIDs *after* a call to setConservedMoieties. I havent worked out how to fix this and so these tests are temporarily disabled. Issue #934 has been added to track this problem.
I've added two new tests that catch this error
TEST_F(RoadRunnerAPITestsWithMCJit, getIdsAfterSetConservedMoiety)
andTEST_F(RoadRunnerAPITestsWithLLJit, getIdsAfterSetConservedMoiety)
but disabled them for the time being. Basically we get a heap buffer overflow error when we do:Here's address sanitizer's output:
These tests pass in Release and Debug builds but fail in when
CMAKE_BUILD_TYPE="Asan"
(which works out of the box on mac, provided sanitizers are installed - windows will be problematic). We may also be able to detect this with valgrind but I haven't tried.I haven't been able to figure out what is going on here but I'm thinking that this is a symptom of the numbers of species changing after the regenerate model associated with the call to setConservedMoieties.
The text was updated successfully, but these errors were encountered: