Closed StephanGocht closed 2 years ago
I could track this back to glibc code for loading dynamically linked libraries. Hence my explanation is that VeriPB eats all the memory (but not too much so that it does not run out of memory itself) and then tries to load an additional dynamically linked library, which fails. I do not think there is too much we can do about it.
During high memory usage with active memory limit (ulimit) it can happen that VeriPB terminates with return code 127, which is usually used for command not found.
If this happens we get the following error message:
cannot allocate memory for thread-local data: ABORT