Menu
▾
▴
#63 Debug On Real Files - can't configure
New
nobody
None
Medium
Defect
2014-06-20
2012-02-29
Anonymous
No
Originally created by: anega...@gmail.com
SDK/Debugger version: 0.3.4
Eclipse version: 3.7.2, Indigo Service Release 2
Google Chrome/V8 Embedder + version: what? Node.JS here
OS + version: Linux Ubuntu 11.10
What steps will reproduce the problem?
1. Trying to debug local files, following instructions from this page https://code.google.com/p/chromedevtools/wiki/FeatureDebugOnRealFiles and repeating after this video: https://code.google.com/p/chromedevtools/wiki/FeatureDebugOnRealFiles
2. Nothing works, Eclipse never stops at my breakpoints in real files - only in VirtualProject files.
3. Have no idea what it
What is the expected result?
Debug local files
What happens instead?
Nothing. Breakpoints are skipped, and I have no idea how to see what is wrong.
Please provide any additional information below. If possible, attach a
(reduced) test-case.
I made a screencast http://www.youtube.com/watch?v=gLi6sIFWEXs
Sorry for blinking ugly low quality crap - this is how screencasts works on my laptop/Ubuntu 11.10.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: sejm...@gmail.com
Did you set up the javascript source mapper? Did you set your break point from the Run menu, or did you let the ChromeDevTools unaware editor set an incompatible breakpoint? I think the Wiki describes this potential issue.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: pavelmaximov81@gmail.com
I had the same problem, setting to "Chrome /V8 breakpoints" in Run > Breakpoint Type solved the problem to me. From that point on whatever JS editor i use inside eclipse (also Aptana JS editor) all the breakpoints are correctly taken by Chrome.