blob: 00362415ad31acf3fa00da116287adccd57aa33c [file] [log] [blame]
/*
* Copyright (c) 2017, 2018, 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/jdwp/EventRequest/Clear/clear001.
* VM Testbase keywords: [quick, jpda, jdwp]
* VM Testbase readme:
* DESCRIPTION
* This test performs checking for
* command set: EventRequest
* command: Clear
* event kind: BREAKPOINT
* Test checks that debuggee accept tested command and replies
* with correct reply packet. Also test checks that no breakpoint
* events occurs for cleared BREAKPOINT request.
* Test consists of two compoments:
* debugger: clear001
* debuggee: clear001a
* First, debugger uses nsk.share support classes to launch debuggee
* and obtain Transport object, that represents JDWP transport channel.
* Next, debugger waits for tested class loaded into debuggee and
* makes request for BREAKPOINT at method run().
* Then, debugger creates creates command packet for command
* EventRequest.Clear with created requestID, sends it to debuggee,
* waits for reply packet and check that reply is correct and has
* no reply data.
* Then, debugger resumes debuggee and waits for an VM_DEATH event.
* If received event is BREAKPOINT event, debugger complains an error.
* Finally, debugger disconnects debuggee, waits for it exits
* and exits too with proper exit code.
* COMMENTS
* Test was fixed due to test bug:
* 4797978 TEST_BUG: potential race condition in a number of JDWP tests
*
* @library /vmTestbase /test/hotspot/jtreg/vmTestbase
* /test/lib
* @run driver jdk.test.lib.FileInstaller . .
* @build nsk.jdwp.EventRequest.Clear.clear001
* nsk.jdwp.EventRequest.Clear.clear001a
* @run main/othervm PropertyResolvingWrapper
* nsk.jdwp.EventRequest.Clear.clear001
* -arch=${os.family}-${os.simpleArch}
* -verbose
* -waittime=5
* -debugee.vmkind=java
* -transport.address=dynamic
* -debugee.vmkeys="${test.vm.opts} ${test.java.opts}"
*/