- This topic has 6 replies, 3 voices, and was last updated 21 years, 2 months ago by
.
-
Posts
-
When I set a break point in the source, the corresponding thread is suspended, but I cannot determine the value of any variables. All are stating ” . . . cannot be resolved”.
Any ideas?
Roger
Roger,
For Java classes, JSP’s what? Walk us through exactly what you’re doing, what you’re expecting, and what you’re seeing and we can probably help.
Scott,
I am trying to debug java classes that are supporting struts action classes. I set a break point in a method, and the assciated thread is suspended, but as I step through the code, when I attempt to inspect a variable, that is typically passed as an argument or instantiated within the method, I get a . . . “cannot be resolved” message when I expand the variable expression in the Debug-Expression window.
I am using ant to build the application EAR file, so the first thing that I checked was to make sure that the compiler was being passed a debug=”on” parameter. I am using BEAs JRockit for both the compilation and the same JDK in my project.
Thanks much!
Roger
Scott,
I should also add that this applies only to local variables. Also, in the debug window, next to the display of the class name under the thread, it is stated that “[local variables unavailable]”
Roger
Roger,
JRockit is known to optimize quite a bit. How about trying JDK 1.4.1 as your default in the workspace and to launch the server (1.4.2 may be problematic) to see if that resolves the issue. If so, you’ll know it’s the JDK difference.
Also, when you use Ant, please bear in mind that they change the defaults and properties quite a bit with each release. For example, you’re using debug=”on” , but I’ve seen them change flags from “on” to “true” and vice versa even between minor releases. You might check that very closely also.
