P4
currently to support assert tests(TEST_VM_ASSERT_MSG), we have the next code in vmassert macro:
if (is_executing_unit_tests()) { \
report_assert_msg(__VA_ARGS__); \
}
it prints assert message, so the test can check that this message is correct. we have to have some extra code because we disable regular fatal error reporting for assert tests (since we do not want to have output and disk be polluted by unneeded crash info from passed assert tests).
there is a couple issues w/ current implementation, there is no info about location (file/line) where assert happens, so it'll be hard to investigate failure from assert tests. it supports only vmassert, so there is no way to test other hotspot errors such as fatal, guarantee, etc.
if (is_executing_unit_tests()) { \
report_assert_msg(__VA_ARGS__); \
}
it prints assert message, so the test can check that this message is correct. we have to have some extra code because we disable regular fatal error reporting for assert tests (since we do not want to have output and disk be polluted by unneeded crash info from passed assert tests).
there is a couple issues w/ current implementation, there is no info about location (file/line) where assert happens, so it'll be hard to investigate failure from assert tests. it supports only vmassert, so there is no way to test other hotspot errors such as fatal, guarantee, etc.