blob: e196970bf18161a83cf98bb6708eeb9013367654 [file] [log] [blame]
/*
* Copyright (c) 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/jdi/BScenarios/multithrd/tc04x001.
* VM Testbase keywords: [quick, jpda, jdi]
* VM Testbase readme:
* DESCRIPTION:
* This test is from the group of so-called Borland's scenarios and
* implements the following test case:
* Suite 2 - Breakpoints (multiple threads)
* Test case: TC4
* Description: Exception breakpoint
* Steps: 1.Set method breakpoint on Main.foo()
* 2.Debug Main
* 3.Stops on line 27 in Main.java
* The description was drown up according to steps under JBuilder.
* Of course, the test has own line numbers and method/class names and
* works as follow:
* When the test is starting debugee, debugger creates MethodEntryRequest.
* After MethodEntryEvent arrived, debugger checks method name and if
* the one corresponds to specified name, it checks line number of the
* event location. It should be 64th line, that is method tc04x001a.foo.
* In case, when at least one event doesn't arrive during waittime
* interval or line number of event is wrong, test fails.
* COMMENTS:
* Test was fixed according to test bug:
* 4778296 TEST_BUG: debuggee VM intemittently hangs after resuming
* - handling VMStartEvent was removed from the debugger part of the test
* - quit on VMDeathEvent was added to the event handling loop
*
* @library /vmTestbase
* /test/lib
* @run driver jdk.test.lib.FileInstaller . .
* @build nsk.jdi.BScenarios.multithrd.tc04x001
* nsk.jdi.BScenarios.multithrd.tc04x001a
* @run main/othervm PropertyResolvingWrapper
* nsk.jdi.BScenarios.multithrd.tc04x001
* -verbose
* -arch=${os.family}-${os.simpleArch}
* -waittime=5
* -debugee.vmkind=java
* -transport.address=dynamic
* "-debugee.vmkeys=${test.vm.opts} ${test.java.opts}"
*/