Bug 210977 - NPE debugging Javascript
Summary: NPE debugging Javascript
Status: NEW
Alias: None
Product: DLTK
Classification: Technology
Component: Common-Debug (show other bugs)
Version: 0.95   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Timur Shipilov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 211074
Blocks:
  Show dependency tree
 
Reported: 2007-11-26 15:42 EST by Jeff McAffer CLA
Modified: 2008-05-26 03:06 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2007-11-26 15:42:47 EST
in the latest stable build (nov 9) I get the following NPE when lanching a simple test.js file.  Note that I am running this on top of the latest Eclipse 3.4 platform builds.

I;ve never used the DLTK JS support so am not sure if I am using it right but debugging gets me this problem and running does not seem to do anything...

Note also that originally I was getting an error looking for the DefaultRhinoRunner class from rhino.dbgp.  I looked in that bundle and tweaked it to export the package including that class.  this seemed to address the issue but I still do not see any output and cannot debug.

This is the test file I'm using.

function x() {
   var i;
   for( i=0; i<20; i++ ) {
      println( " " + i );
   }
   return i;
}

var result = x();

!ENTRY org.eclipse.core.jobs 4 2 2007-11-26 15:33:55.509
!MESSAGE An internal error occurred during: "Launching test.js".
!STACK 0
java.lang.NullPointerException
        at org.eclipse.dltk.launching.DebuggingEngineRunner.addDebugTarget(DebuggingEngineRunner.java:71)
        at org.eclipse.dltk.launching.DebuggingEngineRunner.initialize(DebuggingEngineRunner.java:96)
        at org.eclipse.dltk.internal.launching.debug.JavaScriptAndJDTDebuggerRunner.run(JavaScriptAndJDTDebuggerRunner.j
ava:34)
        at org.eclipse.dltk.javascript.launching.JavaScriptLaunchConfigurationDelegate.runRunner(JavaScriptLaunchConfigu
rationDelegate.java:25)
        at org.eclipse.dltk.launching.AbstractScriptLaunchConfigurationDelegate.launch(AbstractScriptLaunchConfiguration
Delegate.java:799)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:764)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:614)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:827)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1030)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Jeff McAffer CLA 2007-11-27 10:20:25 EST
cc'ing Darin for personal interest
Comment 2 Andrey Platov CLA 2007-11-27 11:15:48 EST
Launching/debug with Rhino is broken when DLTK plugins delivered as JARs (normally). Current code assumed that plugins are delivered in unpacked form. Bug 211074 will address temporarily solution.
Comment 3 Andrey Platov CLA 2008-05-26 03:06:22 EDT
bulk version set: 0.95