[Webkit-unassigned] [Bug 59926] New: Debugger call frame line numbers are inaccurate if your file contains getter or setter declarations

[bugzilla-daemon at webkit.org]

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

           Summary: Debugger call frame line numbers are inaccurate if
                    your file contains getter or setter declarations
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.6
            Status: UNCONFIRMED
          Severity: Critical
          Priority: P1
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: rackley at atlassian.com


Created an attachment (id=91907)
 --> (https://bugs.webkit.org/attachment.cgi?id=91907&action=review)
test file to reproduce the problem

If you have a file that uses getter/setter syntax similar to

TestObject.prototype={
  get prop(){
    return 0;
  }
}

The line numbers become skewed in the parser/debugger call frame. For each one of these in your file, the parser seems to add 2 or 3 extra lines to the current line count. 

I first noticed this problem when trying to debug the Web Inspector. It is currently impossible to accurately step through the Web Inspector using the debugger since this syntax is used quite frequently by it.

I've attached a simple test case that reproduces the problem on the nightly build. There is an html file and script. If you set a breakpoint on line 6 of test.html and step into the function call, you will notice that you step into the function a few lines forward from the proper place. I've verified that this line number is being received from the backend and it isn't a bug in the inspector. 

This seems to have been happening for a while. This is probably the cause of Bug 42252.

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