CODEWITHSUNDEEP
androideclipsedebuggingcrash
Tim C
Tim C

Reputation: 635

Eclipse debug crash problems

For some reason, I can hardly debug anything without Eclipse throwing up a crash error every other step. I'm debugging Android on Eclipse 4.2. The error I get says:

'JDI Event Dispatch' has encountered a problem.
An internal error occurred during: "JDI Event Dispatch".

An internal error occurred during: "JDI Event Dispatch".
java.lang.UnsupportedOperationException

In the Error Log, I get:

eclipse.buildId=I20120608-1400
java.version=1.7.0_02
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product

Error
Fri Mar 15 20:53:09 CDT 2013
An internal error occurred during: "JDI Event Dispatch".

java.lang.UnsupportedOperationException
    at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler(MirrorImpl.java:292)
    at org.eclipse.jdi.internal.MethodImpl.bytecodes(MethodImpl.java:345)
    at org.eclipse.jdt.internal.debug.core.model.JDIMethod.isGetterMethod(JDIMethod.java:86)
    at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.locationIsFiltered(JDIThread.java:2559)
    at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.locationShouldBeFiltered(JDIThread.java:2525)
    at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.handleEvent(JDIThread.java:2477)
    at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:152)
    at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:100)
    at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:249)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Also according to the Error Log, the error is taking place in the Plug-in or.eclipse.core.jobs. Any help would be appreciated, I'm finding it very difficult to work without a debugger!

Upvotes: 1

Views: 2013

Answers (3)

Eric Woodruff
Eric Woodruff

Reputation: 6410

I worked around these error by disabling step filtering. Seems like it was the filter simple getters option.

Upvotes: 5

Alex Gittemeier
Alex Gittemeier

Reputation: 5373

It may have something to do with the name of the method. For example this method:

getFirstValueInBundles(String key, String defaultValue, Bundle... bundles) {
     ...
}

Causes the same exact stack trace on a step-in or step-over. Try changing the name of the method to something that doesn't use get...() :

firstValueInBundles(String key, String defaultValue, Bundle... bundles) {
     ...
}

Then method can be debugged normally.

If this fixes your problem, I will open a bug report and post its id here.

Upvotes: 2

codeMagic
codeMagic

Reputation: 44571

It sounds like maybe a timeout issue in Eclipse. Here is a link to a Similar SO question. It looked like there was a bug report regarding this error through Eclipse's website but didn't seem to have any answers. I hope this can help you.

Since I mentioned the "expressions" tab, you can get JDI errors sometimes if you have certain expressions in there that Eclipse isn't able to deal with. While unrelated to your specific problem, it could be helpful to someone searching for something similar. Here is a SO answer of mine regarding it

Upvotes: 0

Related Questions