8375062: vmTestbase/nsk/jdb/exclude/exclude001/exclude001.java fails to output debuggee prompt after cont cmd

Reviewed-by: dholmes, sspitsyn
This commit is contained in:
Chris Plummer 2026-05-29 17:05:17 +00:00
parent 7dbc83a3bd
commit d4b6c78f3a

View File

@ -1,5 +1,5 @@
/*
* Copyright (c) 2002, 2018, Oracle and/or its affiliates. All rights reserved.
* Copyright (c) 2002, 2026, 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
@ -35,8 +35,13 @@ import java.util.*;
/* This is debuggee aplication */
public class exclude001a {
public static void main(String args[]) {
exclude001a _exclude001a = new exclude001a();
System.exit(exclude001.JCK_STATUS_BASE + _exclude001a.runIt(args, System.out));
// The following will cause intialization of a bunch of classes before we
// enable MethoEntry/Exit events, which would otherwise result in long test runs.
// See JDK-8375062. Also see MyThread.run() below, which is where this came from.
String caltype = GregorianCalendar.getInstance().getCalendarType();
exclude001a _exclude001a = new exclude001a();
System.exit(exclude001.JCK_STATUS_BASE + _exclude001a.runIt(args, System.out));
}
static void lastBreak () {}