Run libjdwp tests with coredump=y
To aid in investigating b/70918330 run with coredump=y. This will
cause libjdwp to abort(3) when an error occurs. This should cause the
runtime to dump a stack which we can use to determine the actual
error.
Test: ./art/tools/run-libjdwp-tests.sh --mode=host
Bug: 70918330
Change-Id: I4f1e1a9873e17661667dfcc1d632ea94b29957d2
diff --git a/tools/run-libjdwp-tests.sh b/tools/run-libjdwp-tests.sh
index bd05251..0bea6a5 100755
--- a/tools/run-libjdwp-tests.sh
+++ b/tools/run-libjdwp-tests.sh
@@ -121,4 +121,5 @@
verbose_run ./art/tools/run-jdwp-tests.sh \
"${args[@]}" \
--jdwp-path "libjdwp.so" \
+ --vm-arg -Djpda.settings.debuggeeAgentExtraOptions=coredump=y \
--expectations "$expect_path"