SDM Debugging not possible - java.lang.NullPointerException

[marian lux]

I did the same steps as described here http://sdbg.github.io/ in this video with gwt 2.7 and always get the error after launching "Launch Chrome" in Debug mode.

An internal error occurred during: "Launching SDM Debug".

java.lang.NullPointerException

See the picture above:

I did this with my current working project (mgwt 2.0 with gwt 2.7) and a new gwt-test-project (greeting service as described in the video).

Always the same problem.

I run Eclipse Luna, GPE installed on Ubuntu 14.04 with Google Chrome 40 beta, 39 and Chromium installed on my machine.

Maybe Chromium is the problem? Because in "Launch Chrome" I can see the chromium logo as you can see in the picture above.

[Ivan Markov]

Nope - the icon is not the problem, as it is hard-coded in the application (and should be the Chrome, not Chromium icon, but that's another small issue).

Would you send me your Eclipse error log so I can see in details the exception stacktrace? 

You can retrieve it from Help -> About Eclipse -> Installation Details -> View error log

Another useful thing would be if you enable Tracing for SDBG from Window -> Preferences -> Tracing -> Enable tracing and then send me the trace log as well (once you try to launch the app at least once)

[marian lux]

This are the error logs for the exception from two tests:

!ENTRY org.eclipse.core.jobs 4 2 2014-11-27 07:47:12.873
!MESSAGE An internal error occurred during: "Launching SDM TestGWT".
!STACK 0
java.lang.NullPointerException
        at com.github.sdbg.debug.core.internal.util.BrowserManager.buildArgumentsList(BrowserManager.java:370)
        at com.github.sdbg.debug.core.internal.util.BrowserManager.startNewBrowserProcess(BrowserManager.java:899)
        at com.github.sdbg.debug.core.internal.util.BrowserManager.launchBrowser(BrowserManager.java:303)
        at com.github.sdbg.debug.core.configs.ChromeLaunchConfigurationDelegate.doLaunch(ChromeLaunchConfigurationDelegate.java:97)
        at com.github.sdbg.debug.core.SDBGLaunchConfigurationDelegate.launch(SDBGLaunchConfigurationDelegate.java:51)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

!ENTRY org.eclipse.core.jobs 4 2 2014-11-27 08:04:26.011
!MESSAGE An internal error occurred during: "Launching SDM TestGWT".
!STACK 0
java.lang.NullPointerException
        at com.github.sdbg.debug.core.internal.util.BrowserManager.buildArgumentsList(BrowserManager.java:370)
        at com.github.sdbg.debug.core.internal.util.BrowserManager.startNewBrowserProcess(BrowserManager.java:899)
        at com.github.sdbg.debug.core.internal.util.BrowserManager.launchBrowser(BrowserManager.java:303)
        at com.github.sdbg.debug.core.configs.ChromeLaunchConfigurationDelegate.doLaunch(ChromeLaunchConfigurationDelegate.java:97)
        at com.github.sdbg.debug.core.SDBGLaunchConfigurationDelegate.launch(SDBGLaunchConfigurationDelegate.java:51)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

In attachment you can find the trace.

Thank you
-- Marian

[Ivan Markov]

Thanks a lot for the trace file & the stacktrace. In the latest release, I've introduced a regression when locating the Chrome executable on Linux: https://github.com/sdbg/sdbg/issues/81

This issue is now fixed, so please upgrade your SDBG plugin from Eclipse -> Help -> Install New Software -> (choose the SDBG update site from the list), and then let me know the result - thanks again!

 

[marian lux]

Thank you very much for the prompt fix!

Both projects work now with debugging SDM in Eclipse. This is really a leap forward for using SDM and I think its time for me to quit with classic Devmode.

Thanks again

-- Marian

[samowre]

Funny, I am having the exact same issue as Mariam first described. I have only started using this plugin today so my initial plugin update rev is 0.9.6 (which should include the fix, right???).  I am using Eclipse 4.4, GWT 2.7, Chrome 39.

Install details: JavaScript Debugger with Source Mapping Support 0.9.6.201411271907 com.github.sdbg.feature.feature.group sdbg.github.org

Here is the logger entry.

!ENTRY org.eclipse.core.jobs 4 2 2014-11-28 13:35:06.322
!MESSAGE An internal error occurred during: "Launching Recall Scheduler - Debug".
!STACK 0
java.lang.NullPointerException
	at com.github.sdbg.debug.core.internal.util.BrowserManager.buildArgumentsList(BrowserManager.java:370)
	at com.github.sdbg.debug.core.internal.util.BrowserManager.startNewBrowserProcess(BrowserManager.java:902)
	at com.github.sdbg.debug.core.internal.util.BrowserManager.launchBrowser(BrowserManager.java:303)
	at com.github.sdbg.debug.core.configs.ChromeLaunchConfigurationDelegate.doLaunch(ChromeLaunchConfigurationDelegate.java:97)
	at com.github.sdbg.debug.core.SDBGLaunchConfigurationDelegate.launch(SDBGLaunchConfigurationDelegate.java:51)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:883)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

!ENTRY org.eclipse.equinox.p2.publisher.eclipse 4 0 2014-11-28 13:42:15.352
!MESSAGE Unable to acquire PluginConverter service during generation for: C:\Eclipse\eclipse_4_4\plugins\gwt-2.7.0.

!ENTRY org.eclipse.equinox.p2.publisher.eclipse 4 0 2014-11-28 13:42:15.456
!MESSAGE Unable to acquire PluginConverter service during generation for: C:\Eclipse\eclipse_4_4\plugins\gwt-2.7.0.

[samowre]

I should note that I am on Windows 8.1 x64.

[Ivan Markov]

The reason for this error is that SDBG cannot locate the Chrome executable on your OS.

I looked again and besides the breakage of the Chrome location algorithm on Linux (which is indeed fixed in 0.9.6), it seems I've, errr, regressed the *reporting* message box that informs you that SDBG cannot find the Chrome executable. That's why you get a NPE exception instead of proper error message.

To cut the long story short, please install the 0.9.7 release which I just pushed to p2, however have in mind that it will *not* fix the problem for you completely. Instead, this release will just properly report to you that the Chrome executable cannot be located. Now, *why* it could not be located on your Windows 8.1 I don't know yet. If you enable SDBG tracing (as I asked Marian to do) and then send me the trace log - that is likely to give me more information to look at the root cause. In addition to the trace log, it would be useful to tell me what is the installation location of your chrome executable.

[samowre]

0.9.7 prints a better error message. I added the chrome.exe location to my eclipse.ini as it suggests and all is well. Great tool you have here. Now I'm getting greedy and want unobfuscated variable names in the debugger!  :-)

Here is the path to chrome on Windows 8.1 x64.

C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

For anyone else who stumbles on this post, just add this to the bottom of your eclipse.ini file.

-Dchrome.location=C:\Program Files (x86)\Google\Chrome\Application\chrome.exe