Recent changes to DebuggerTutorial

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: peter.ry...@gmail.com

Yes, this is this one: http://code.google.com/p/chromedevtools/issues/detail?id=65

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: andy.war...@gmail.com

I received a NullPointerException? as well. It went away when I enabled “Show debugger network communication console” in the Debug Configuration (shown in picture above), and now it's working fine for me.

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: peter.ry...@gmail.com

Guys, could you please submit the NPE as an issue in issues http://code.google.com/p/chromedevtools/issues This is a wiki-page. I would also need a stack trace if possible. See also http://code.google.com/p/chromedevtools/wiki/HowToReportProblem (and if you don't see a stack trace). Thank you

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: pletnev.rusalex

I have the same problem: java.lang.NullPointerException? Fedora 16 Eclipse SDK Version: 3.7.0 Build id: I20110613-1736 Chrome: 18.0.1025.162 ChromeDevTools? SDK WIP Backends 0.1.6.201202250216 ChromeDevTools? SDK 0.3.4.201202250214 Chromium JavaScript? Debugger Bridge to JSDT 0.3.4.201202250214 Chromium JavaScript? Remote Debugger 0.3.4.201202250214

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: don41...@googlemail.com

Same problem over here. I got the chrome 18.0.1025.14 (german) and got a NullPointerException? after trying to connect. Chrome Dev Tools:

ChromeDevTools? SDK WIP Backends 0.1.6.201202250216 Chromium JavaScript? Debugger Bridge to JSDT 0.3.4.201202250214 Chromium JavaScript? Remote Debugger 0.3.4.201202250214

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: peter.ry...@gmail.com

Here's what can be done:

Please confirm that your debug configuration is in Auto-detect source look-up mode (first tab in debug configuration)
When debugging, open your file properties and in "V8 JavaScript? Script" page check what debugger tells about remote script for this file.
When debugging, in "Breakpoints" view (near "Variables") open "Breakpoint Properties" and in "Technical Info" page check what debugger think about your breakpoint (must be something about regexp).
In debug configuration enable "Show debugger network communication console" (make require Eclipse restart) and in protocol dump console check that setting a breakpoint actually causes remote message roundtrip.

As to each folder/parent folder, I guess you are choosing "Workspace Folder" container type, it has "Search subfolders" options that governs this.

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: mike.cop...@gmail.com

also do you have to list each source folder or just the parent folder?

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: mike.cop...@gmail.com

Thanks for the info but, still not working. Must be something I'm missing Here is what I do:

1. Run Chrome with --remote-shell-port=9222

2. open url http://localhost:8888/my_project_folder/

3. From Eclipse: I debug my project: right click my project > select Debug As > Debug Configurations > select the Chromium Javascript debug configuration. In Source tab I added the path to my files (mamp/htdocs/my_project_folder)

4. In the debug perspective, I select > Run > Breakpoint types > Chrome / V8 Breakpoints

still no luck. ****Is it possible that the debugger is confused because my Source files are the ones that are currently being run by Chrome?

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:46 -0000

Originally posted by: peter.ry...@gmail.com

The is a correct link.

Discussion for DebuggerTutorial page

Anonymous — Sat, 25 Apr 2015 13:43:45 -0000

Originally posted by: peter.ry...@gmail.com

It's a common deal with breakpoint types that we should probably highlight better. See EclipseDebuggerFeatures#Selecting_Breakpoint_Type? for details.

How have you set up your source look-up? Was it 'Auto-detect' (better) or 'Exact match'?

With 'Auto-detect' your breakpoints (of correct type) should work. However you'll have to manually list your folder under a Sources in debug configuration so that debugger highlighted your files.