Debugger dies

Former Member
Former Member
That's something I could never get to work for more than a few moves (steps over or into). The debugger causes Eclipse to hang or it just dies with one error or another.

SDK 2.4.5, Eclipse Oxygen 3.A (fully updated), Windows 10.

Error:

(would've been nice if I could paste an image :) ), but the error says:

'Debug Source Lookup' has encountered a problem. An internal error occurred during: "Debug Source Lookup" (seems like an error that likes to repeat itself...) ..."An internal error occurred during: "Debug Source Lookup". java.lang.NullPointerException".

I had the debugger die in the past with older versions of the SDK and Eclipse as well - never could have more than 2 minutes of it.

More details from Eclipse:

The following will be send to: Eclipse


REPORT

eclipseBuildId 4.7.3.M20180330-0640
eclipseProduct org.eclipse.epp.package.java.product
javaRuntimeVersion 1.8.0_131-b11
osgiWs win32
osgiOs Windows10
osgiOsVersion 10.0.0
osgiArch x86_64

STATUS

pluginId org.eclipse.core.jobs
pluginVersion 3.9.3.v20180115-1757
code 2
severity 4
message An internal error occurred during: "Debug Source Lookup".
fingerprint d192ac8e984642a4c27bb9c265a4e51f

Exception:java.lang.NullPointerException: null
at org.eclipse.debug.internal.ui.views.launch.SourceNotFoundEditorInput.<init>(SourceNotFoundEditorInpu t.java:52)
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.lookup(SourceLookupFacility.java:362 )
at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$SourceLookupJob.run(SourceLookupFaci lity.java:746)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)


BUNDLES

name org.eclipse.core.jobs
version 3.9.3.v20180115-1757

name org.eclipse.debug.ui
version 3.12.50.v20170920-1329
  • Former Member
    Former Member
    Hey,

    I've been able to reproduce this in house partially. Though i'm not able to reproduce the hang or crash in Eclipse I am able to see the debugger error. I've got a ticket to be worked by one of our engineers created.

    Thanks,
    - Coleman
  • Former Member
    Former Member
    I've been digging into this and discovered that the crash I'm getting happens when I try to step into a native function of the CIQ virtual machine. These function are not open in a public SDK in the way something like JAVA would be. So I'm getting Eclipse errors when it goes looking for a file that doesn't exist in the CIQ SDK directory. We are having a discussion on better ways to address this. I'll get back to as soon as I know more.

    Thanks,
    - Coleman