Issue metadata
Sign in to add a comment
|
Unable to debug eval'd scripts by reaching the script from console
Reported by
sume...@ohumhealthcare.com,
Apr 28 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. load and eval script in javascript 2. enter desired function name in console, click on the function which will take you to the vm file for the eval'd script 3. place a breakpoint on a line within the file/function What is the expected behavior? I should be able to debug within the eval'd script, placing a breakpoint should allow me to proceed to that breakpoint in Dev Tools What went wrong? As soon as I place the breakpoint, it goes away. This was working on earlier version of chrome, after auto-upgrade of chrome this has stopped working. Did this work before? Yes Dont remember Chrome version: 57.0.2987.133 Channel: n/a OS Version: 10.0 Flash Version:
,
Apr 28 2017
I probably can guess the root of this issue. It's problem with breakpoint manager for anonymous script if two or more targets have script with the same scriptId, manager tries to set breakpoint in both and if one fails (one should fails most of the time since scriptId collision is just accident) then manager just removes breakpoint as illegal. I'll fix it soon.
,
Apr 28 2017
@sumeetc, thanks for the report! To confirm my guess, could you navigate chrome to about:blank page, and repeat your steps and confirm that breakpoint continue to disappear?
,
Apr 29 2017
I can confirm that the breakpoint is working when i perform the steps in the about:blank page. So this definitely points out to the reason in your previous comment.
,
May 19 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dgozman@chromium.org
, Apr 28 2017Labels: -Pri-2 Pri-1
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)