Correct behavior of thread suspension around Raw monitors
The interaction between raw monitors and thread suspension was
different than some real-world agents expected. Real-world agents rely
on the RawMonitorWait function acting as a suspend point.
Changed the raw-monitor implementation to match this behavior.
Add tests for this behavior and for the behavior of RawMonitorExit
(which does not act as a suspend point).
Bug: 66904725
Bug: 62821960
Test: ./test.py --host -j50
Test: ./art/tools/run-libjdwp-tests.sh --mode=host
Change-Id: Ibaed6a7e6910b7b612f0fb1313958857fbe54595
diff --git a/test/1943-suspend-raw-monitor-wait/run b/test/1943-suspend-raw-monitor-wait/run
new file mode 100755
index 0000000..e92b873
--- /dev/null
+++ b/test/1943-suspend-raw-monitor-wait/run
@@ -0,0 +1,17 @@
+#!/bin/bash
+#
+# Copyright 2017 The Android Open Source Project
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+./default-run "$@" --jvmti