Closed Bug 471066 Opened 16 years ago Closed 16 years ago

debugger keyword in joes-original [@ call_enumerate]

Categories

(Firefox :: General, defect)

3.5 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 462851

People

(Reporter: johnjbarton, Unassigned)

References

Details

(Whiteboard: )

Install Firebug eg http://getfirebug.com/releases/firebug/1.4X/firebug-1.4X.0a11.xpi Open joe's original test: http://getfirebug.com/tests/console/joes-original/test.html Click on 'debugger in JSON' http://crash-stats.mozilla.com/report/index/71b3b683-5762-4b1a-8d22-c731e2081224 It crashes after jsd.enterNestedEventLoop, on a call_enumerate. I guess it gets to eval(req.responseText); in breakpoints.js and hits "debugger" triggering the debugger. Somewhere in the debugger UI setup must be an enumerate on a bad object. The title of the bug report reflect my current limited understanding.
Flags: blocking-firefox3.1?
Whiteboard: [firebug-p1]
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Summary: [crash] debugger keyword in joes-original @call_enumerate → debugger keyword in joes-original [@ call_enumerate]
removing blocking flag from duplicate bug
Flags: blocking-firefox3.1?
Tested, is fixed in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090105 Shiretoko/3.1b3pre
Whiteboard: [firebug-p1] →
You need to log in before you can comment on or make changes to this bug.