• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 324
  • Last Modified:

JBuilder Fatal Error

Hey experts,

When I am using JBuilder 6.0 to compile java programs in debug mode (& only in debug mode - this problem is not happening in normal run mode), sometimes when I stop the program by pressing the end button (or closing the applet), the compiler terminates immediately (JBuilder directly closes - without leaving any warning), and I have to restart it again. The following error log would be left:


**********************************************************************

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=C:\JB\JBuilder6\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(SharedMemoryConnection.java:61)
      at com.sun.tools.jdi.TargetVM.run(TargetVM.java:97)
      at java.lang.Thread.run(Thread.java:484)

Dynamic libraries:
0x00400000 - 0x00405000       C:\JB\JBuilder6\jdk1.3.1\bin\java.exe
0x77F50000 - 0x77FF7000       C:\WINDOWS\System32\ntdll.dll
0x77E60000 - 0x77F46000       C:\WINDOWS\system32\kernel32.dll
0x77DD0000 - 0x77E5D000       C:\WINDOWS\system32\ADVAPI32.dll
0x78000000 - 0x78087000       C:\WINDOWS\system32\RPCRT4.dll
0x77C10000 - 0x77C63000       C:\WINDOWS\system32\MSVCRT.dll
0x6D420000 - 0x6D4EF000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\hotspot\jvm.dll
0x77D40000 - 0x77DCC000       C:\WINDOWS\system32\USER32.dll
0x7E090000 - 0x7E0D1000       C:\WINDOWS\system32\GDI32.dll
0x76B40000 - 0x76B6C000       C:\WINDOWS\System32\WINMM.dll
0x76390000 - 0x763AC000       C:\WINDOWS\System32\IMM32.DLL
0x629C0000 - 0x629C8000       C:\WINDOWS\System32\LPK.DLL
0x72FA0000 - 0x72FFA000       C:\WINDOWS\System32\USP10.dll
0x6D220000 - 0x6D227000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\verify.dll
0x6D250000 - 0x6D266000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\java.dll
0x6D3C0000 - 0x6D3CD000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\zip.dll
0x6D020000 - 0x6D128000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\awt.dll
0x73000000 - 0x73023000       C:\WINDOWS\System32\WINSPOOL.DRV
0x771B0000 - 0x772D4000       C:\WINDOWS\system32\ole32.dll
0x6D1E0000 - 0x6D21B000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\fontmanager.dll
0x51000000 - 0x51047000       C:\WINDOWS\System32\DDRAW.dll
0x73BC0000 - 0x73BC6000       C:\WINDOWS\System32\DCIMAN32.dll
0x69000000 - 0x690E2000       C:\WINDOWS\System32\tridicdf.dll
0x74720000 - 0x74764000       C:\WINDOWS\System32\MSCTF.dll
0x0F320000 - 0x0F34B000       C:\WINDOWS\System32\msctfime.ime
0x6D340000 - 0x6D348000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\net.dll
0x71AD0000 - 0x71AD8000       C:\WINDOWS\System32\WSOCK32.dll
0x71AB0000 - 0x71AC4000       C:\WINDOWS\System32\WS2_32.dll
0x71AA0000 - 0x71AA8000       C:\WINDOWS\System32\WS2HELP.dll
0x71A50000 - 0x71A8B000       C:\WINDOWS\System32\mswsock.dll
0x76F20000 - 0x76F45000       C:\WINDOWS\System32\DNSAPI.dll
0x76D60000 - 0x76D76000       C:\WINDOWS\System32\iphlpapi.dll
0x76FB0000 - 0x76FB7000       C:\WINDOWS\System32\winrnr.dll
0x76F60000 - 0x76F8C000       C:\WINDOWS\system32\WLDAP32.dll
0x76FC0000 - 0x76FC5000       C:\WINDOWS\System32\rasadhlp.dll
0x71A90000 - 0x71A98000       C:\WINDOWS\System32\wshtcpip.dll
0x746F0000 - 0x74716000       C:\WINDOWS\System32\Msimtf.dll
0x6D1C0000 - 0x6D1C6000       C:\JB\JBuilder6\jdk1.3.1\bin\dt_shmem.dll
0x6D320000 - 0x6D340000       C:\JB\JBuilder6\jdk1.3.1\jre\bin\jsound.dll
0x72D20000 - 0x72D29000       C:\WINDOWS\System32\wdmaud.drv
0x72D10000 - 0x72D18000       C:\WINDOWS\System32\msacm32.drv
0x77BE0000 - 0x77BF4000       C:\WINDOWS\System32\MSACM32.dll
0x77BD0000 - 0x77BD7000       C:\WINDOWS\System32\midimap.dll
0x76C90000 - 0x76CB2000       C:\WINDOWS\system32\imagehlp.dll
0x6D510000 - 0x6D58D000       C:\WINDOWS\system32\DBGHELP.dll
0x77C00000 - 0x77C07000       C:\WINDOWS\system32\VERSION.dll
0x76BF0000 - 0x76BFB000       C:\WINDOWS\System32\PSAPI.DLL

Local Time = Fri Aug 06 09:33:34 2004
Elapsed Time = 260
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 mixed mode)
#

********************************************************************

Only when I preempt the javaw.exe process from the process list in the OS Task Manager, this problem never happens (even in debug mode). I tried JBuilder on several PCs and several OSs, but the problem remained the same. It sometimes happens, not always (almost 40% of the time).

Any Help?
0
mte01
Asked:
mte01
  • 4
  • 3
1 Solution
 
CEHJCommented:
Try installing a new Java sdk (1.4.x) - you are in any case working with an outdated system:

http://java.sun.com/j2se/1.4.2/downloads/index.html
0
 
mte01Author Commented:
I know CEHJ that JBuilder 6.0 (and equivalently sdk 1.3.x)  is outdated, but the company I am doing software development for wants me to stick with this version, I can do nothing about it.
0
 
CEHJCommented:
Try reinstalling that version then:

http://java.sun.com/products/archive/
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
mte01Author Commented:
The Java SDK gets installed with the JBuilder installation wizard. I don't install anything related to Sun Microsystems Java prior to installing Borland JBuilder. I just installed JBuilder 6.0 directly (and repeated the installation like 6 or 7 times to try to avoid the error - all the Java SDK comes with it), and everytime I used to get the error when I run any program in debug mode and then just stop it!
0
 
mte01Author Commented:
Amazing! Really Amazing. It's a simple thing, but I would have never thought of deleting a dll file. (I hope it doesn't cause any run-time errors in the future). Finally, I can debug my programs in a relaxed manner :).

Thanks you CEHJ ;)
0
 
CEHJCommented:
:-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now