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
72
73
|
/*
* 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/VirtualMachine/process/process001.
* VM Testbase keywords: [quick, jpda, jdi]
* VM Testbase readme:
* DESCRIPTION:
* The test for the implementation of an object of the type
* VirtualMachine.
* The test checks up that a result of the method
* com.sun.jdi.VirtualMachine.process()
* complies with its spec:
* public java.lang.Process process()
* Returns the Process object for this virtual machine
* if launched by a LaunchingConnector
* Returns: the Process object for this virtual machine, or
* null if it was not launched by a LaunchingConnector.
* The test case includes only a LaunchingConnector.
* The test works as follows:
* The debugger program - nsk.jdi.VirtualMachine.process.process001;
* the debuggee program - nsk.jdi.VirtualMachine.process.process001a.
* Using nsk.jdi.share classes,
* the debugger gets the debuggee running on another JavaVM,
* creates the object debuggee.VM,
* establishes a pipe with the debuggee program, and then
* send to the programm commands, to which the debuggee replies
* via the pipe. Upon getting reply,
* the debugger calls corresponding debuggee.VM methods to get
* needed data and compares the data got to the data expected.
* In case of error the test produces the return value 97 and
* a corresponding error message(s).
* Otherwise, the test is passed and produces
* the return value 95 and no message.
* COMMENTS:
*
* @library /vmTestbase
* /test/lib
* @build nsk.jdi.VirtualMachine.process.process001
* nsk.jdi.VirtualMachine.process.process001a
* @run driver
* nsk.jdi.VirtualMachine.process.process001
* -verbose
* -arch=${os.family}-${os.simpleArch}
* -waittime=5
* -debugee.vmkind=java
* -transport.address=dynamic
* -debugee.vmkeys="${test.vm.opts} ${test.java.opts}"
*/
|
