Recent changes to FeatureDebugOnRealFiles

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: ErnestJe...@gmail.com

when I click "Run>Breakpoint type", it says "None Available". any ideas?

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: pavelmaximov81@gmail.com

For all who is having problems with breakpoints set in Eclipse being ignored by Chrome check in Elcipse "Run > Breakpoint Type" is set to "Chrome /V8 breakpoints". If it was not, change the setting and recreate your breakpoints they will be of new the type and will work.

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: rghas...@gmail.com

Was any progress ever made with you issue azli? Anyone have a link to the mail group mentioned? I have a similar problem. I am able to set breakpoints in source files an have them hit, but they only open in the virtual project.

Discussion for FeatureDebugOnRealFiles page

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

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

Hi Azlist1 Are you sure that your "source mapper" container is ordered above "Default" container in Source Lookup Path? If Default container goes first, it's natural that virtual file has a priority.

If this doesn't help, I suggest we continue in a mail group so that we don't miss new answers from each other.

Peter

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: azli...@gmail.com

I am unable to map to my real project files. Setting a breakpoint in my original source file works fine. However when the breakpoint is hit at runtime it opens the "Virtual Project" file and not the real one.

I have tried different "source mapper" settings alongside "Exact match" setting toggled on, but nothing will do. I am working on a Java webapplication project that gets deployed to an eclipse managed Tomcat server on localhost.

In source mapper I have tried https://localhost:8443/ as well as https://localhost:8443/MyProject/ With either Java Project, Project, Workspace folder etc.... as "Target Source container" but none of these did the trick of displaying the line breakpoint inside the original file. For now I fall back to "Automatic" script mapping which opens up the Virtual file but I'd really love to see it working the way it should ( I'd like :) ) .

What am I missing ? Any hints appreciated.

Discussion for FeatureDebugOnRealFiles page

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

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

yes, this option was moved to the other tab (Mapping I believe). The text is outdated, thank you for finding this. Peter

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: brunope...@gmail.com

Hi,

I don't see any "Source look-up method" in my configuration window, maybe the plugin was updated since you wrote this page ? Is there a workaround ?

Thanks in advance

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: anega...@gmail.com

I can't get it working with local files: http://code.google.com/p/chromedevtools/issues/detail?id=63&thanks=63&ts=1330541070

Discussion for FeatureDebugOnRealFiles page

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

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

Torsten, no, this shouldn't be like this. Breakpoint is expected to be registered in VM and actually set immediately after the script is loaded. This could be a bug though. I propose you submit an issue with some details. This way you will also get into a mail-loop. Alternatively, we could discuss it in a discussion group (see main page). Peter

Discussion for FeatureDebugOnRealFiles page

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

Originally posted by: tocr...@gmail.com

Hi there,

am I correct in assuming that only breakpoints set '''after''' the corresponding script was loaded into chromium are hit? At least that's what I observe -- once working breakpoints are ignored when clicking chromium's reload button...

Regards --

Torsten