Trac author: michal
Attachment: file:exception.png

Under what circumstances? What Eclipse version?

Trac author: michal
Eclipse Galileo Build id: 20090920-1017
startup config:
-XX:MaxPermSize=256m
-Xms256m
-Xmx1024m
-Xss1M
-server
-XX:+DoEscapeAnalysis -XX:+UseConcMarkSweepGC
-XstartOnFirstThread Exception appears immediately when I start debugging. Nothing else was done before, just opened IDE and started debugging. It is 100% reproducible, I get this message each time when I start debug.

Are you able to debug Java applications with this configuration?

Trac author: michal
yes, without any problems. to make sure I just checked that again. java debugs work ok.

Are you able to extract the full stacktrace?

Trac author: michal
sure. here is what I get on "Details":
Exception processing async thread queue
Exception processing async thread queue
String index out of range: 0
and here is the stacktrace:
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:686)
at org.eclipse.jdt.internal.debug.eval.ast.engine.BinaryBasedSourceGenerator.isAnonymousTypeName(BinaryBasedSourceGenerator.java:495)
at org.eclipse.jdt.internal.debug.eval.ast.engine.BinaryBasedSourceGenerator.buildTypeDeclaration(BinaryBasedSourceGenerator.java:173)
at org.eclipse.jdt.internal.debug.eval.ast.engine.BinaryBasedSourceGenerator.buildTypeDeclaration(BinaryBasedSourceGenerator.java:145)
at org.eclipse.jdt.internal.debug.eval.ast.engine.BinaryBasedSourceGenerator.buildSource(BinaryBasedSourceGenerator.java:74)
at org.eclipse.jdt.internal.debug.eval.ast.engine.EvaluationSourceGenerator.getInstanceSourceMapper(EvaluationSourceGenerator.java:204)
at org.eclipse.jdt.internal.debug.eval.ast.engine.EvaluationSourceGenerator.getSource(EvaluationSourceGenerator.java:216)
at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.getCompiledExpression(ASTEvaluationEngine.java:226)
at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine.evaluate(ASTEvaluationEngine.java:115)
at org.eclipse.jdt.internal.debug.ui.JavaWatchExpressionDelegate$EvaluationRunnable.run(JavaWatchExpressionDelegate.java:144)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$ThreadJob.run(JDIThread.java:2751)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Do you have a watchpoint enabled? On "arr"? (I'm guessing that you're working with the same code sample as in #2990).
If that's the case, could you try removing all watchpoints and let me know if you still get the JDI error.

Trac author: michal
yes, I test it exactly on a code shown in screenshot.
I disabled breakpoint and now debug starts without these JDI exceptions.
Btw. have you also noticed that this issue is very simmilar to one raised by me today (#2990 String index out of range)?
In both cases IDE complains about String index out of bound, maybe this is same cause?

Indeed, I think they both have the same root cause.

Updating tickets (#1000069, #1000195, #1000213, #1000223, #1000006, #1000021, #1000038, #1000048, #1000051, #1000052, #1000075, #1000103, #1000109, #1000115, #1000119, #1000156, #1000186, #1000207, #1000238, #1000262, #1000263, #380, #389, #683, #1238, #1331, #1635, #1645, #1715, #1729, #1744, #1783, #1839, #1869, #1885, #1890, #1902, #1918, #1919, #1924, #1925, #1946, #1964, #1991, #2131, #2233, #2342, #2348, #2408, #2459, #2499, #2523, #2572, #2582, #2602, #2614, #2615, #2675, #2710, #2745, #2763, #2816, #2830, #2834, #2878, #2879, #2887, #2888, #2901, #2911, #2912, #2922, #2937, #2938, #2942, #2951, #2955, #2957, #2961, #2964, #2965, #2974, #2975, #2989, #2990, #3002, #3055, #3070, #3087, #3135, #3139, #3173, #3182, #3184, #3200, #3213, #3214, #3221, #3243, #3251)