Assert failures are ignored in Windows tests

From byron.c....@gmail.com on August 20, 2014 15:45:16

Running a test in which a client assert fails should cause the test to fail, but the assert by default only generates a popup message, which is blocked by the (necessary) setting "-msgbox_mask 0". The assert should secondarily generate output on stderr so that the ctest evaluator observes unexpected output and fails the test. If this cannot be done reliably, then some other mechanism should be used, for example checking the exit code of the tested process.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1520