This happens in JDK1.3.0-P build in Solaris (Not in Windows). When a break point is set the application exits with java.lang.VerifyError.

Steps to reproduce
------------------
1. javac -g Test.java
2. jdb Test
3. stop at Test:6
4. run


--------------------------------------------
jtools>java -version
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-P)
Java HotSpot(TM) Client VM (build 1.3-P, interpreted mode)
jtools>jdb Test
Initializing jdb...
> stop at Test:6
Deferring breakpoint Test:6.
It will be set after the class is loaded.
> run
run Test
Java HotSpot(TM) Client VM warning: Setting of property "java.compiler" is ignored

VM Started: > Set deferred breakpoint Test:6
Exception in thread "main" java.lang.VerifyError: (class: Test, method: main signature: ([Ljava/lang/String;)V) Quick instructions shouldn't appear yet.

The application exited
--------------------------------------------


Test.java
----------
public class Test {

public static void main(String args[]) {

Test test = new Test();
System.out.println(" in test");
}
}

=================================================
I am trying approximately the same thing, but
In build O, I got the following error:

Internal exception:
com.sun.jdi.VMDisconnectedException
at com.sun.tools.jdi.TargetVM.waitForReply(TargetVM.java:282)
at com.sun.tools.jdi.VirtualMachineImpl.waitForTargetReply(VirtualMachineImpl.java:700)
at com.sun.tools.jdi.PacketStream.waitForReply(PacketStream.java:65)
at com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.waitForReply(JDWP.java:482)
at com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.process(JDWP.java:468)
at com.sun.tools.jdi.VirtualMachineImpl.<init>(VirtualMachineImpl.java:174)
at com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMachineManagerImpl.java:166)
at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:121)
at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:153)
at com.sun.tools.example.debug.tty.VMConnection.launchTarget(VMConnection.java:263)
at com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:127)
at com.sun.tools.example.debug.tty.Commands.commandRun(Commands.java:391)
at com.sun.tools.example.debug.tty.TTY.executeCommand(TTY.java:386)
at com.sun.tools.example.debug.tty.TTY.<init>(TTY.java:618)
at com.sun.tools.example.debug.tty.TTY.main(TTY.java:917)

In build N, I got the following error:

run Test
Internal exception:
com.sun.jdi.VMDisconnectedException: Bad file number
at com.sun.tools.jdi.TargetVM.send(TargetVM.java:271)
at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:696)
at com.sun.tools.jdi.PacketStream.send(PacketStream.java:55)
at com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.enqueueCommand(JDWP.java:476)
at com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.process(JDWP.java:467)
at com.sun.tools.jdi.VirtualMachineImpl.<init>(VirtualMachineImpl.java:174)
at com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMachineManagerImpl.java:166)
at com.sun.tools.jdi.AbstractLauncher.launch(AbstractLauncher.java:121)
at com.sun.tools.jdi.SunCommandLineLauncher.launch(SunCommandLineLauncher.java:153)
at com.sun.tools.example.debug.tty.VMConnection.launchTarget(VMConnection.java:263)
at com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:127)
at com.sun.tools.example.debug.tty.Commands.commandRun(Commands.java:391)
at com.sun.tools.example.debug.tty.TTY.executeCommand(TTY.java:386)
at com.sun.tools.example.debug.tty.TTY.<init>(TTY.java:618)
at com.sun.tools.example.debug.tty.TTY.main(TTY.java:917)

Basically, jdb is useless to me at this point.

bradford.wetmore@eng 1999-12-02

=============================================================
This failure is only in JDK 1.3.0-P build as mentioned. In N build and O build the above failures do occur and bug was filed (Refer: 4288718). Try in L or M build.