Closed
Bug 976042
Opened 10 years ago
Closed 10 years ago
Uncaught exception in DebuggerClient.prototype.onPacket/<@resource://gre/modules/devtools/dbg-client.jsm:655
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 975167
People
(Reporter: freddy, Unassigned)
Details
Attachments
(1 file)
2.13 KB,
text/plain
|
Details |
TLDR: Trying to execute code from within the devtools after hitting a breakpoint renders the console non-functional for the current tab. STR: 1. Set a breakpoint (worked on all pages I tested so far) 2. Do something that hits the breakpoint 3. Change to console and 'inspect' something via console autocomplete, e.g., enter |5.|, the dot should trigger the error 4. Console does not execute statements/show results of expressions. Expected Result: 1,2. .. 3. Tooltip shows attributes instead of producing error message 4. Execution within the current breakpoint's state still works. This happens to me in Aurora (build from Feb 23th, 2014). I have obtained the error message from the browser console and attached to this bug. As a workaround, one could close the tab & right-click another tab to "undo close". This loses the state that you wanted to reach with the breakpoint of course.
Reporter | ||
Comment 1•10 years ago
|
||
FWIW, the bug was observed when debugging something on the local filesystem; the very last line of the attached error contains the file URI.
Comment 2•10 years ago
|
||
We have a patch ready to land in bug 975167 that should fix this.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Comment 3•10 years ago
|
||
Frederik, thanks for the bug report. We should probably ask for aurora approval for the patch in bug 975167.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•