search

win-hi / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
0 stars 0 forks source link

Debug On Real Files - can't configure #63

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
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 
http://code.google.com/p/chromedevtools/wiki/FeatureDebugOnRealFiles and 
repeating after this video: 
http://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.

Original issue reported on code.google.com by anega...@gmail.com on 29 Feb 2012 at 6:44

GoogleCodeExporter commented 8 years ago 
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.

Original comment by sejm...@gmail.com on 2 May 2012 at 5:04

GoogleCodeExporter commented 8 years ago 
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.

Original comment by pavelmaximov81@gmail.com on 20 Jun 2014 at 5:40