Comment #5 on issue 321 by [email protected]: CHECK failed: ... "((trace)) !=
(0)" (0x0, 0x0)
http://code.google.com/p/address-sanitizer/issues/detail?id=321
Why not exit with a signal code on CHECK failure? The 'not' utility will
return non-zero if the subprocess exits due to a signal instead of a normal
non-zero exit code. This makes it so that mainline LLVM tests using not
fail properly when an assertion fails. Calling abort() is probably
inappropriate in the sanitizer, but maybe some other approach is OK.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
"address-sanitizer" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
