[Webkit-unassigned] [Bug 32064] New: [js-debugger] Step out behaves unexpected

[bugzilla-daemon at webkit.org]

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

           Summary: [js-debugger] Step out behaves unexpected
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: spamfaenger at gmx.de


When debugging a statement like this:

-- snip --
task.story().isCollapsed()
-- snap --

it is quite hard to step into the second function call (isCollapsed()) with
webkit.

This is not exactly easy with other debuggers too, but what most of them do
(gdb most importantly) is if you use step into on that statement you get into
story(), and if you step out from that you get back to the original statement -
but before isCollapsed() is called.

Webkit sadly doesn't behave this way - but it should (thats the bug report).

One workaround which works sometimes is to to step into story and then step to
the last statement therein - then step over that twice, which lets the focus
remain in that method, and then press step into again.

That at least gets you into the second method - however very clumsily. (Which
could be argued is a second bug actually)

So please improve the way the debugger works so that step out only steps out of
the current function and not also of  all subsequent calls on the return value
from that function.

Regards,
Martin

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