1651dc9668
The CTestTestMemcheck test cases all try to check the ctest output with a regular expression. They fail intermittently due to ordering of the portions of the output that come from stdout and stderr being mixed. Convert all the test cases to use the RunCMake infrastructure to match stdout and stderr separately.
14 lines
445 B
Plaintext
14 lines
445 B
Plaintext
Memory checking results:
|
|
data race - 1
|
|
data race on vptr \(ctor/dtor vs virtual call\) - 1
|
|
heap-use-after-free - 1
|
|
thread leak - 1
|
|
destroy of a locked mutex - 1
|
|
double lock of a mutex - 1
|
|
unlock of an unlocked mutex \(or by a wrong thread\) - 1
|
|
read lock of a write locked mutex - 1
|
|
read unlock of a write locked mutex - 1
|
|
signal-unsafe call inside of a signal - 1
|
|
signal handler spoils errno - 1
|
|
lock-order-inversion \(potential deadlock\) - 1
|