'Toggle Line Breakpoints' has encountered a problem Resource '/ /index.js.chromium' does not exist.

[pebanfield]

Breakpoints are not working in my install. I've tried a fresh mac 64bit eclipse install. I am running OSX version 10.8.3.

The debugger runs and attaches, but when I try to add a breakpoint to any .chromium version of my source I get the error in the title.

Does anyone have any ideas of what I could try to resolve the issue? Thanks.

Peter

[paulvi]

Please confirm, that you are using the latest 0.4 version. And exact Eclipse version, e.g. 4.2.2 Eclipse for JEE developers.

    How do I? -- StackOverflow!
    I got this error, why? -- StackOverflow!
    I got this error and I'm sure it's a bug -- file an issue!
    I have an idea/request -- file an issue!
    Why do you? -- the mailing list!
    When will you? -- the mailing list!

Should you report a bug, please include the following:

    Eclipse version number (like 4.2.2 or 3.8.0)
    A detailed description of the steps necessary to reproduce the problem.
    The '.log' file from the directory '.metadata' in your workspace.

[pebanfield]

I'm not exactly sure how to confirm. Looking in my eclipse plug-ins directory there appears to be two versions - 0.3.8 and 0.3.9. But this install is the result of using the following update url

http://chromedevtools.googlecode.com/svn/update/dev/

How/where do I specify the version I want to install? My eclipse install says

Eclipse Java EE IDE for Web Developers.

Version: Indigo Service Release 2 Build id: 20120216-1857

I don't know where to locate the version number. The release notes say

Release 3.7.2 Last revised Feb 7, 2012

It would be helpful if there were links maintained to the download for the recommended/supported versions of eclipse for the nodeclipse plugin. I've always found this challenging with eclipse. Once I have the correct version will this change what version of nodeclipse I get when I use the update url? I will try to re-install.

Thanks very much for your help.

Peter

[tomotaro1065]

Hi @pebanfield,

Probably this issue is not related with the version of Eclipse and chromedevtools. Indigo is no problem for nodeclipse. Chromedevtools 0.3.9 is OK. If you use the following update site or Eclipse Marketplace(http://marketplace.eclipse.org/content/nodeclipse), currently version of nodeclipse is 0.4.0 .

http://www.nodeclipse.org/updates

Please check out your eclipse plugins folder. The following files exist?

org.nodeclipse.debug0.4.0..jar org.nodeclipse.ui0.4.0..jar

Thanks.

[pebanfield]

Hi - I've just tried with a fresh eclipse install and have updated from market place. This has resulted in version org.chromium.debug_0.3.9.201305191444 of the plug-in. Is it possible that this version has not been updated for mac os 64 bit version? I don't know how update works under the hood so just a guess. Thanks.

Peter

[pebanfield]

Yes and I'm still having the same issue. Thanks

[pebanfield]

Oh and sorry this has resulte in org.nodeclipse.ui_0.4.0.201305191444 as well, but the issue still persists. Thanks.

[pebanfield]

and org.nodeclipse.ui_0.4.0.201305191444

[tomotaro1065]

Could you paste here the contents of .log file which is located under .metadata folder? .metadata folder is located under workspace.

[pebanfield]

So - I started to try to locate the log file for you and found that the log file had not been updated recently. I also noticed that there were a lot of back up versions.

I was using the same workspace as I had used for previous eclipse installs and so I decided that would try with a new clean workspace. Now debugging is working as expected! I'm not sure why but apparently something in the old workspace was hosing up debugging.

Thanks for your help!

Peter

[tomotaro1065]

Congratulations.