Closed
Bug 924259
Opened 8 years ago
Closed 8 years ago
Extremely poor error message when starting httpd.js server on port that's in use
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla27
People
(Reporter: billm, Assigned: billm)
Details
Attachments
(1 file)
823 bytes,
patch
|
Waldo
:
review+
|
Details | Diff | Splinter Review |
As mistakes go, this is a pretty common one. When it happens, this is all we print: System JS : ERROR (null):0 uncaught exception: 2147746065 Improving the error handler in xpconnect seems hard since we don't have any kind of exception object to attach a stack trace or filename/line number information to. However, we can at least print something useful when it happens.
Attachment #814262 -
Flags: review?(jwalden+bmo)
Updated•8 years ago
|
Attachment #814262 -
Flags: review?(jwalden+bmo) → review+
Assignee | ||
Comment 1•8 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/bcadc378309d
https://hg.mozilla.org/mozilla-central/rev/bcadc378309d
Assignee: nobody → wmccloskey
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
Updated•3 years ago
|
Component: httpd.js → General
You need to log in
before you can comment on or make changes to this bug.
Description
•