Java Debugger/Execution Analyzer not working

[davijeb]

I'm a Java developer with over 10 years experience but I simply cannot get the Java debugger to work in EA.

I have the Ultimate version. Am using the samples project provided by EA and have tried every possible combination of classpath/jre there is but to no avail.

The code compiles fine.

My build script looks like:

Code: [Select]

"%JAVA_HOME%\bin\javac.exe" -verbose -g -cp "%classpath%;." %r*.java and that works just fine.

My debug script looks like:

Code: [Select]

jre=%JAVA%\jre
where %JAVA% points to

Code: [Select]

C:\Program Files (x86)\Java\jre6.

The full trace I see when I run the debugger is:


[04137243]      Warning, no java.class.path property set, defaulting to environment variable if present
[04137243]      Warning, no CLASSPATH environment variable present on system, defaulting to E:\workspace\ea\Java\Java\Collector
[04137244]      classpath used will be:-
[04137244]      -Djava.class.path=E:\workspace\ea\Java\Java\Collector;
[04137321]      Stack recording threshold set to 4 frames


The classpath looks ok and if I override the debug script and use:

Code: [Select]

-Djava.class.path=E:\workspace\ea\Java\Java\Collector;.;
The output then just displays

[04673609]      Stack recording threshold set to 4 frames


There is no error. There is no log I can see. There is nothing in the windows events.

Does anyone have a clue what is happening here? It's frustrating that such a great product lets itself down by not providing a rich enough feedback loop when these issues are encountered. I've seen other devs post exactly the same issue but I've not seen any explanation as to the cause yet.

I hope to hear from someone [insert appropriate smiley here]

Cheers,

(Frustrated) Jez

[Doug Blake]

Frustrating for us too, what does Ahhhggggghhhhh mean? I had to open this post to find out its not of interest to me...

[davijeb]

Good point Doug. Apologies, late night frustrations...

[BruceLee]

Probably it is to late for Doug, but...the solution for this problem is as follows:
You need to inform EA where jvm.dll file is located on your machine, for example if jvm.dll is located in C:\Java\jdk1.7\jre\bin\client, then you need to put this information in the Java Virtual Machine Options of an Analyzer Script (debug script ).
So, you need to open the script, then select Debug>Platform, and under the Java Virtual Machine Options label, you need to enter jre= C:\Java\jdk1.7\jre\bin\client
In my case, this solved the problem.

If Java is located under "Program files", it also can cause similar problem (EA is having some struggles using the "Program Files" directories). If this is a case then try something like this:
Instead of C:\Program Files\Java\jdk1.7
You can write (or similar): C:\PROGRA~1\Java\jdk1.7
Try in Dos prompt: dir C:\PROGRA~1
 8-)  Osss