RESOLVED FIXED 32064
Web Inspector: Debugger step out behaves unexpected 
https://bugs.webkit.org/show_bug.cgi?id=32064
Summary Web Inspector: Debugger step out behaves unexpected
Martin Häcker
Reported 2009-12-02 05:02:35 PST
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
Attachments
Add attachment proposed patch, testcase, etc.
Rob Colburn
Comment 1 2012-05-10 14:27:35 PDT
The script debug tools have improved quite a bit since 2009. @Martin what's the status here, have your needs been fulfilled?
Martin Häcker
Comment 2 2012-05-25 02:31:09 PDT
Works for me
Note You need to log in before you can comment on or make changes to this bug.