1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
/*
* Copyright (c) 2018, 2024, Oracle and/or its affiliates. All rights reserved.
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* This code is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License version 2 only, as
* published by the Free Software Foundation.
*
* This code is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
* version 2 for more details (a copy is included in the LICENSE file that
* accompanied this code).
*
* You should have received a copy of the GNU General Public License version
* 2 along with this work; if not, write to the Free Software Foundation,
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
*
* Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
* or visit www.oracle.com if you need additional information or have any
* questions.
*/
/*
* @test
*
* @summary converted from VM Testbase nsk/jdi/ObjectReference/waitingThreads/waitingthreads003.
* VM Testbase keywords: [quick, jpda, jdi]
* VM Testbase readme:
* DESCRIPTION:
* The test checks an following assertion of
* com.sun.jdi.ObjectReference.waitingThreads method spec:
* Returns a List containing a ThreadReference for each thread currently
* waiting for this object's monitor.
* There are two test cases:
* - An object with no waiting threads.
* A list with zero size is expected to be returned by the method.
* - An object with threads waiting to lock monitor in a synchronized method.
* The debugger checks with expected results:
* - a size of returned list of ThreadReferences,
* - the names of thread references,
* - whether the thread reference has the same contented monitor object
* as checked one.
* The debugger program - nsk.jdi.ObjectReference.waitingThreads.waitingthreads004;
* the debuggee program - nsk.jdi.ObjectReference.waitingThreads.waitingthreads004a.
* Communication details between the debugger and the debuggee:
* Using nsk.jdi.share classes, the debugger connects to debuggee program running
* on another VM and establishes a communication pipe with the debuggee. The pipe
* is used in bi-directional way by sending and receiving special commands between
* the debugger and debuggee for synchronization
* In case of error the test produces the exit code 97 and a corresponding error
* message(s). Otherwise, the test is passed and produces the exit code 95 and
* no message.
* COMMENTS:
* 4883502 TEST_BUG: waiting Threads testcases not predictable
*
* @library /vmTestbase
* /test/lib
* @build nsk.jdi.ObjectReference.waitingThreads.waitingthreads003
* nsk.jdi.ObjectReference.waitingThreads.waitingthreads003a
* @run driver
* nsk.jdi.ObjectReference.waitingThreads.waitingthreads003
* -verbose
* -arch=${os.family}-${os.simpleArch}
* -waittime=5
* -debugee.vmkind=java
* -transport.address=dynamic
* -debugee.vmkeys="${test.vm.opts} ${test.java.opts}"
*/
|
