Community
Participate
Working Groups
Build 20030211(take2) When placing a breakpoint in MethodVerifier.checkMethods(), debugger will hit it, but refuse to display local variables. Steps: - sources for JDT/Core (from same build) - put breakpoint in MethodVerifier#checkMethod (first line) - create Java project to launch Java compiler: - create Java project 'BatchCompile' - add org.eclipse.jdt.core on its classpath - define Compile.java type with following contents: [import org.eclipse.jdt.internal.compiler.batch.Main; import org.eclipse.jdt.internal.compiler.util.Util; public class Compile { public static void main(String[] args) { Main.compile( "d:/eclipse/workspaces/dev2.0/plugins/BatchCompile/src/X.java " + " -1.4 -source 1.4 -preserveAllLocals - warn:unusedArgument " + " -cp d:/jdk1.4.1/jre/lib/rt.jar " + " -d d:/eclipse/workspaces/dev2.0/plugins/BatchCompile/bin" + " -verbose");] - note that path to X.java and rt.jar may need to be adjusted. - add unit X.java with contents: [ public class X { { new SomeInterface(){ public void foo(int someParamX$1){} }; } } interface SomeInterface { void foo(int someParam); }] - run 'Compile' as a Java application in debug mode against JRE 1.4.1 Once the breakpoint is hit, no variable is available.
Olivier - could you pls double check that our dbg attributes are ok ?
My Java settings were: compiler 1.4 compliant, but source level 1.3 and target level 1.1.
Tried compiler 1.4 and default souce/target (1.4/1.2). Didn't change the behavior.
MethodVerifier from HEAD reproduces it.
Default 1.3 compliant mode also reproduces it.
None of the methods in the stackframe provide any variable information. I highly doubt we would be misgenerating all their attributes.
Using JRE 1.3.1 (Sun) did not change the behavior either. Nothing is reported in the .log.
Olivier - ignore my previous comment about verifying our attributes. This is a known debugger issue. When closing Debug view, and resetting perspective, it did the trick. I thought this defect had been fixed in this build though...
I just finished to build my self-hosting workspace to investigate the problem...
*** This bug has been marked as a duplicate of 30971 ***