Hi Mike, Looks like you pressed "stop" button while debugging. The crash may happen when using shared memory transport for debugging (this is JPDA bug). Socket transport behaves much better so it is preferable to use it.
Best regards, Eugene Zhuravlev IntelliJ Software, http://www.intellij.com/ "Develop with pleasure!" ----- Original Message ----- From: Mike Liu To: Eap-List@Intellij. Com Sent: 27 November, 2001 6:25 AM Subject: [Eap-list] Exception on Pandora, as follows: An unexpected exception has been detected in native code outside the VM. Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6d1c2349 Function name=(N/A) Library=D:\java\jdk1.3.1\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.receivePacket0(Native Method) at com.sun.tools.jdi.SharedMemoryConnection.receivePacket(SharedMemoryConnectio n.java:61) at com.sun.tools.jdi.TargetVM.run(TargetVM.java:97) at java.lang.Thread.run(Thread.java:484) Local Time = Sat Nov 24 10:22:12 2001 Elapsed Time = 1815 # # The exception above was detected in native code outside the VM # # Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode) # _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
