[Webkit-unassigned] [Bug 20683] New: Script Debugger is partly paused, partly not when stopping at a breakpoint in eval()'d code.
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Sep 6 00:40:16 PDT 2008
https://bugs.webkit.org/show_bug.cgi?id=20683
Summary: Script Debugger is partly paused, partly not when
stopping at a breakpoint in eval()'d code.
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh
OS/Version: Mac OS X 10.5
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: millenomi at gmail.com
When the Script Debugger has a breakpoint set in eval()'d code, stopping at
that breakpoint leaves the debugger window in an undesirable "mixed" state.
Parts of it think it's paused (notably the step controls at the top right of
the window, which report 'Paused'), while other parts think it's not (notably
the Scope Variables and Call Stack views, which report "Not Paused", and the
current line indication highlight, which isn't shown).
Step-in, step-out, step-over and continue controls work, but not having the
current line highlight makes them hard to use.
A minimal test case:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html>
<head>
<title></title>
</head>
<body>
<script>
eval("window.someFunction = function() {\nalert('Hello,
world!');\n};");
</script>
<button onclick="window.someFunction();">Test script</button>
</body>
</html>
To trigger the bug, do the following:
1. Open the page and enable the Script Debugger.
2. From the debugger file list, choose "(program)" to see the eval'd code
listing.
3. Place a breakpoint in line 2 of the listing.
4. Click the button in the page.
(This bug makes debugging cappuccino.org scripts rather difficult,
unfortunately.)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list