[Webkit-unassigned] [Bug 93473] Web Inspector: The front-end should provide the position in original source file when set a breakpoint

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=93473





--- Comment #3 from Yury Semikhatsky <yurys at chromium.org>  2012-08-08 23:46:43 PST ---
(In reply to comment #0)
> I'd like to discuss here, should we provide the the position in original source file when set a breakpoint. For example, a JS statement like this:
> [space][space][space]var[space]a=1;
> The position in original source file is (0,3), but now front-end send (0,0) when set a breakpoint, the heading spaces are removed.
> To accommodate it, JSC has to add code to meet the same rules of removing leading space.
> 
I'm not sure about JSC but in case of V8 it was that we couldn't break at some statements, e.g. if you set a breakpoint at line "var c = a + b;" it could move to line "f();". The functionality was added for cases like this but it handles setting breakpoint at a space equally well by finding nearest statement.

function f() {}
var a = 10;
var b = Date.now();
var c = a + b;
f();

So basically we could only break at call stubs, branching operators and loops. That was improved some time ago but you should keep in mind that the breakpoint can move not only because of spaces.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.