609N/A# @summary exercise HotSpot error handling code 609N/A# Repeatedly invoke java with a command-line option that causes HotSpot to 609N/A# produce an error report and terminate just after initialization. Each 609N/A# invocation is identified by a small integer, <n>, which provokes a different 609N/A# error (assertion failure, guarantee failure, fatal error, etc.). The output 609N/A# The automated checking done by this script is minimal. When updating the 609N/A# fatal error handler it is more useful to run it manually or to use the -retain 609N/A# option with the jtreg so that test directories are not removed automatically. 609N/A# export TESTJAVA TESTVMOPTS 609N/Aulimit -c
0 # no core files "${assert_re}${tail_1}" "${assert_re}${tail_2}" \
"${guarantee_re}${tail_1}" "${guarantee_re}${tail_2}" \
"${fatal_re}${tail_1}" "${fatal_re}${tail_2}" \
"${fatal_re}.*truncated" "ChunkPool::allocate" \
"ShouldNotCall" "ShouldNotReachHere" \
# If ErrorHandlerTest is ignored (product build), stop. # Using the built-in variable $! to get the pid does not work reliably on # windows; use a wildcard instead. echo "ErrorHandlerTest=$i failed ($f)"