ingrid.yao@Eng 2001-07-12
Same problem can be reproduced on both Sparc and WinNT machine.
--------- Bug reported by a CAP member -----------------------
J2SE Version (please include all output from java -version flag):
java version "1.4.0-beta_refresh"
Java(TM) 2 Runtime Environment, Standard Edition (build1.4.0-beta_refresh-b66)
Java HotSpot(TM) Client VM (build 1.4.0-beta_refresh-b66, mixed mode)
Does this problem occur on J2SE 1.3? Yes / No (pick one)
Yes.
Operating System Configuration Information (be specific):
Win2k, no service packs
Hardware Configuration Information (be specific):
AMD Athlon 1GHz / MSI K7TPro2A
60GB HDs
512MB RAM
Bug Description:
Second attempt to attach to JVM via JDI results in exception & crashes
monitored JVM.
If the monitoring JVM disconnects without properly shutting down the
connection, a following attempt to attach to the same JVM results in
an internal exception & crashes the monitored JVM.
Some of the time the error is preceded by the OS error:
The instruction at 0x6d29d568 referenced memory at 0x0000001c. The
memory could not be "read". (Debugging reported an error in JDWP.DLL)
Error in monitoring JVM console:
--------------------------------
N:\jdk14TestProject>java com.sun.tools.example.debug.tty.TTY -attach
javadebug
Internal exception: com.sun.jdi.VMDisconnectedException
at com.sun.tools.jdi.TargetVM.waitForReply(TargetVM.java:275)
at com.sun.tools.jdi.VirtualMachineImpl.waitForTargetReply(VirtualMachineImpl.java:849)
at com.sun.tools.jdi.PacketStream.waitForReply(PacketStream.java:54)
at
com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.waitForReply(JDWP.java:549)
at
com.sun.tools.jdi.JDWP$VirtualMachine$IDSizes.process(JDWP.java:535)
at
com.sun.tools.jdi.VirtualMachineImpl.<init>(VirtualMachineImpl.java:176)
at
com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMachineManagerImpl.java:162)
at
com.sun.tools.jdi.VirtualMachineManagerImpl.createVirtualMachine(VirtualMachineManagerImpl.java:170)
at
com.sun.tools.jdi.SharedMemoryAttachingConnector.attach(SharedMemoryAttachingConnector.java:47)
at
com.sun.tools.example.debug.tty.VMConnection.attachTarget(VMConnection.java:337)
at
com.sun.tools.example.debug.tty.VMConnection.open(VMConnection.java:167)
at com.sun.tools.example.debug.tty.Env.init(Env.java:68)
at com.sun.tools.example.debug.tty.TTY.main(TTY.java:437)
Error in monitored JVM console:
------------------------------
Transport error, error code = -1
FATAL ERROR in native method: JDWP "util.c" (May 30 2001), line 1097:Unexpected error, error code = 50 (JVMDI_ERROR_INVALID_MONITOR)
<JVM crashes/terminates>
<the "FATAL ERROR" above does not always show up...>
Steps to Reproduce (be specific):
1) Start any app (e.g. SimpleExample demo) - (monitored app)
2) Start (example/debug/)TTY app (monitoring app)
3) Control-C from TTY app
4) Start TTY app again --> exception occurs, #1 terminates
- duplicates
-
JDK-4487683 JDWP: VM crash induced by abruptly disconnecting jdb then reconnecting
-
- Closed
-