JDK-4409562 : JVM crashed when debugging in Forte
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmdi
  • Affected Version: 1.3.1
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2001-01-30
  • Updated: 2001-03-12
  • Resolved: 2001-03-12
Related Reports
Relates :  
JDK-4420844 - JPDA: Debugger operations after VM death cause errors
Description
When I am debugging in Forte for Java using JPDA debugger the JVM
in which Forte is running sometimes crashes. It happens only
on Windows (on Linux and Solaris it works fine).

The crashed VM generated the following report:
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x501c227f
Function name=(N/A)
Library=C:\jdk1.3\bin\dt_shmem.dll

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.

Current Java thread:
	at com.sun.tools.jdi.SharedMemoryConnection.sendPacket0(Native Method)
	at com.sun.tools.jdi.SharedMemoryConnection.sendPacket(SharedMemoryConnection.java:71)
	at com.sun.tools.jdi.TargetVM.send(TargetVM.java:258)
	at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:691)
	at com.sun.tools.jdi.PacketStream.send(PacketStream.java:44)
	at com.sun.tools.jdi.JDWP$ThreadReference$Status.enqueueCommand(JDWP.java:3552)
	at com.sun.tools.jdi.JDWP$ThreadReference$Status.process(JDWP.java:3538)
	at com.sun.tools.jdi.ThreadReferenceImpl.jdwpStatus(ThreadReferenceImpl.java:187)
	at com.sun.tools.jdi.ThreadReferenceImpl.isSuspended(ThreadReferenceImpl.java:203)
	at org.netbeans.modules.debugger.jpda.JPDAThread.isSuspended(JPDAThread.java:224)
	at org.netbeans.modules.debugger.jpda.JPDAWatch.canValidate(JPDAWatch.java:135)
	at org.netbeans.modules.debugger.support.util.Validator$1.run(Validator.java:85)
	at org.netbeans.modules.debugger.support.util.Task.run(Task.java:113)
	at org.netbeans.modules.debugger.support.util.RequestProcessor$ProcessorThread.run(RequestProcessor.java:565)

Dynamic libraries:
0x00400000 - 0x0041E000 	E:\Forte4j\Pilsen010122\bin\runide.exe
0x77F80000 - 0x77FF9000 	C:\WINNT\System32\ntdll.dll
0x77DB0000 - 0x77E0A000 	C:\WINNT\system32\ADVAPI32.dll
0x77E80000 - 0x77F36000 	C:\WINNT\system32\KERNEL32.DLL
0x77D40000 - 0x77DAF000 	C:\WINNT\system32\RPCRT4.DLL
0x77E10000 - 0x77E75000 	C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000 	C:\WINNT\system32\GDI32.DLL
0x6D420000 - 0x6D4ED000 	C:\jdk1.3.1\jre\bin\hotspot\jvm.dll
0x77570000 - 0x775A0000 	C:\WINNT\System32\WINMM.dll
0x78000000 - 0x78046000 	C:\WINNT\system32\MSVCRT.dll
0x6D220000 - 0x6D227000 	C:\jdk1.3.1\jre\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 	C:\jdk1.3.1\jre\bin\verify.dll
0x6D250000 - 0x6D266000 	C:\jdk1.3.1\jre\bin\java.dll
0x6D3C0000 - 0x6D3CD000 	C:\jdk1.3.1\jre\bin\zip.dll
0x6D020000 - 0x6D128000 	C:\jdk1.3.1\jre\bin\awt.dll
0x77800000 - 0x7781D000 	C:\WINNT\System32\WINSPOOL.DRV
0x75E60000 - 0x75E7A000 	C:\WINNT\System32\IMM32.dll
0x77A50000 - 0x77B45000 	C:\WINNT\system32\ole32.dll
0x6D1E0000 - 0x6D21B000 	C:\jdk1.3.1\jre\bin\fontmanager.dll
0x72800000 - 0x72846000 	C:\WINNT\System32\DDRAW.dll
0x728A0000 - 0x728A6000 	C:\WINNT\System32\DCIMAN32.dll
0x69000000 - 0x691D7000 	C:\WINNT\System32\G400ICD.DLL
0x6E420000 - 0x6E426000 	C:\WINNT\System32\INDICDLL.dll
0x1EB40000 - 0x1EB4B000 	C:\PROGRA~1\STAROF~1\TRAYHOOK.dll
0x775A0000 - 0x777E0000 	C:\WINNT\system32\SHELL32.dll
0x77C70000 - 0x77CBA000 	C:\WINNT\system32\SHLWAPI.DLL
0x77B50000 - 0x77BDA000 	C:\WINNT\system32\COMCTL32.DLL
0x6D340000 - 0x6D348000 	C:\jdk1.3.1\jre\bin\net.dll
0x75050000 - 0x75058000 	C:\WINNT\System32\WSOCK32.dll
0x75030000 - 0x75044000 	C:\WINNT\System32\WS2_32.DLL
0x75020000 - 0x75028000 	C:\WINNT\System32\WS2HELP.DLL
0x74FD0000 - 0x74FE1000 	C:\WINNT\system32\msafd.dll
0x75010000 - 0x75017000 	C:\WINNT\System32\wshtcpip.dll
0x77840000 - 0x7784C000 	C:\WINNT\System32\rnr20.dll
0x77980000 - 0x779A4000 	C:\WINNT\System32\DNSAPI.DLL
0x777E0000 - 0x777E8000 	C:\WINNT\System32\winrnr.dll
0x77950000 - 0x77979000 	C:\WINNT\system32\WLDAP32.DLL
0x501C0000 - 0x501C6000 	C:\jdk1.3\bin\dt_shmem.dll
0x777F0000 - 0x777F5000 	C:\WINNT\System32\rasadhlp.dll
0x77830000 - 0x7783E000 	C:\WINNT\System32\RTUTILS.DLL
0x77920000 - 0x77942000 	C:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000 	C:\WINNT\system32\DBGHELP.dll
0x12A60000 - 0x12A6B000 	C:\WINNT\System32\PSAPI.DLL

Local Time = Mon Jan 29 15:45:59 2001
Elapsed Time = 156
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1beta-b14 mixed mode)
#
Comments
PUBLIC COMMENTS The JVM crashed while debugging in Forte on Windows
10-06-2004
EVALUATION This crash is occurring in the JDWP shared memory transport. This code is only used on win32 platforms. robert.field@Eng 2001-02-1 The crash occurs at the stack trace shown in the description, followed by these native funcs: native code: waitForSpace(connection, &connection->outgoing) native code: sendBytes(connection,.... native code: shmemBase_sendPacket(connection, &packet); The waitForSpace func does this: if ( stream->shared->isFull && ... (where 'stream' is the 2nd input param, ie, &connection->outgoing) The EXCEPTION appears to occur on the cmp instruction that accesses the isFull field. I suppose this means that the 'shared' field in the Stream has gotten clobbered. james.holmlund@Eng 2001-02-14 This bug is classic VM, and since HotSpot is now supporting JVMDI, we are closing this bug as will not fix. I've checked with submitter to get approval for closing this. janet.koenig@Eng 2001-03-12
12-03-2001