After fixing bug 1479330 I do see ASAN warnings from epicsExceptionTest where it also causes 2 tests to fail, but this is probably to be expected given what the code there is doing:
tux-vm-rhel7% ./epicsExceptionTest
1..4
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
not ok 1 - new char[18446744073709551615] returned (nil)
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
ok 2 - new (nothrow) returned (nil)
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
not ok 3 - new char[18446744073709551615] returned (nil)
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
ok 4 - new (nothrow) returned (nil)
After fixing bug 1479330 I do see ASAN warnings from epicsExceptionTest where it also causes 2 tests to fail, but this is probably to be expected given what the code there is doing:
tux-vm-rhel7% ./epicsExceptio nTest 3709551615] returned (nil) 3709551615] returned (nil)
1..4
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
not ok 1 - new char[1844674407
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
ok 2 - new (nothrow) returned (nil)
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
not ok 3 - new char[1844674407
==11845== WARNING: AddressSanitizer failed to allocate 0xffffffffffffffff bytes
ok 4 - new (nothrow) returned (nil)
Results
=======
Tests: 4
Passed: 2 = 50.00%
Failed: 2 = 50.00%