RESOLVED WORKSFORME 42252
Web Inspector: [JSC] [REGRESSION] Breakpoints don't work on some functions
https://bugs.webkit.org/show_bug.cgi?id=42252
Summary Web Inspector: [JSC] [REGRESSION] Breakpoints don't work on some functions
Nikita Vasilyev
Reported 2010-07-14 05:57:32 PDT
http://screenr.com/obR 0:19—0:25 Breakpoint doesn't work, but it works few days ago. 0:30—0:37 Breakpoint works. 0:42 Line numbers messed up. In screencast I use latest weekly build. I can reproduce the same bug on a build, which was built via "build-webkit". I don't figure out how to make a reduction, sorry.
Attachments
Nikita Vasilyev
Comment 1 2010-07-14 06:07:03 PDT
s/works/worked/ s/don't/didn't/ Line numbers in Timeline Panel messed up too.
Nikita Vasilyev
Comment 2 2010-07-17 00:01:54 PDT
Can we someone find the bad commit and undo it? I tried to debug https://bugs.webkit.org/show_bug.cgi?id=42476, but without breakpoints it's not very pleasant task.
Pavel Feldman
Comment 3 2010-07-17 00:42:50 PDT
(In reply to comment #2) > Can we someone find the bad commit and undo it? I tried to debug https://bugs.webkit.org/show_bug.cgi?id=42476, but without breakpoints it's not very pleasant task. Works fine on Chromium - this is likely to be a JSC parser issue. For things not to block you, try getting latest Chromium from http://build.chromium.org/buildbot/continuous/?C=N;O=D, run it with ~/Downloads/chrome-mac-XX/Chromium.app/Contents/MacOS/Chromium --process-per-tab And you'll be able to debug inspector using Inspect Element / Cmd+Opt+I. > Line numbers in Timeline Panel messed up too. Safari does not yet show line numbers on timeline. Chromium works fine for me on latest. Which lines are wrong?
Nikita Vasilyev
Comment 4 2010-07-17 01:07:58 PDT
> Safari does not yet show line numbers on timeline. Chromium works fine for me on latest. Which lines are wrong? Whoops, I meant Profiles. http://screenr.com/eVR 0:44–1:08 Wrong line number 1:32–1:45 OK 1:55–2:02 Wrong line number
Ryan Ackley
Comment 5 2011-05-02 04:01:49 PDT
I've run into the exact same problem and I think I've narrowed down the cause. See Bug 59926
Brian Burg
Comment 6 2014-11-29 17:43:47 PST
Please re-open with a test case if this issue is still relevant.
Note You need to log in before you can comment on or make changes to this bug.