Issue 63 in chromedevtools: Debug On Real Files - can't configure
chromed...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 63 by anega...@gmail.com: Debug On Real Files - can't configure
http://code.google.com/p/chromedevtools/issues/detail?id=63
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.
Peter Rybin
Sorry for the late answer. I was on vacation.
Thank you for your screencast. However there are some details missing.
Here's what I can think of right now.
1. There are 2 source look-up modes now. In version 0.3.0 new Auto-
detect mode was added ( http://code.google.com/p/chromedevtools/wiki/Release_0_3_0#Auto-Detect_Source_Look-Up_Mode
). Unfortunately the wiki-page you referred to misses this. Thank you
very much for pointing this out, we should update it soon. I would
recommend using auto-detect fuzzy look-up mode unless you want a
strict mapping.
2. From your video it's not clear which look-up mode is enabled in
your debug configuration. Since you are using JavaScript Source Name
Mapper, "Exact match" must be selected.
3. I can't see a file structure under your original project. The file
"test.js" must be exactly inside a subfolder chain "all" => "modules"
=> "nodejs" all inside a source folder "sites" that you chose on
video.
Please feel free to ask further.
Peter
On Feb 29, 10:45 pm, chromedevto...@googlecode.com wrote:
> Status: New
> Owner: ----
> Labels: Type-Defect Priority-Medium
>
> 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/FeatureDebugOnRealFilesand
> 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.
>
chromed...@googlecode.com
Comment #1 on issue 63 by sejm...@gmail.com: Debug On Real Files - can't
configure
http://code.google.com/p/chromedevtools/issues/detail?id=63
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.
chromed...@googlecode.com
Comment #2 on issue 63 by pavelma...@gmail.com: Debug On Real Files -
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.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings