Closed Bo-Yuan-Huang closed 4 years ago
Also, it seems to be a c++17 filesystem problem due to compiler library mismatch. https://stackoverflow.com/questions/56738708/c-stdbad-alloc-on-stdfilesystempath-append
(However, this issue only happens in OSX, not the Ubuntu as mentioned.)
Error message:
unit_tests(59330,0x10937edc0) malloc: can't allocate region
:*** mach_vm_map(size=3758289336431292416, flags: 100) failed (error code=3)
unit_tests(59330,0x10937edc0) malloc: *** set a breakpoint in malloc_error_break to debug
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
Using TestVlgVerifInvSyn.LoadInvFromBeginning
as the entry point, the issue seems to happen at:
Describe the bug C++ exception
std::bad_alloc
is found in several unit tests, e.g.,TestVlgVerifInvSyn.SimpleCntCegar
andTestSmtParse.ChcParse
.To Reproduce This issue seems to be platform dependent (lack of robustness). Within the early investigation, implicit and opened files seem to be relevant.
Environment (please complete the following information):
Additional context Will be address in the PR #187.