Extremely poor error message when starting httpd.js server on port that's in use

RESOLVED FIXED in mozilla27

Status

Product:
Testing
Component:
General
Type:
defect
Status:
RESOLVED FIXED
Opened:
6 years ago
Updated:
2 years ago

People

(Reporter: billm, Assigned: billm)

Tracking

Version:
unspecified
Target:
mozilla27
Platform:
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

socket-in-use
823 bytes, patch
Waldo
: review+
Details | Diff | Splinter Review
Posted patch socket-in-use — — 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)
Attachment #814262 - Flags: review?(jwalden+bmo) → review+
https://hg.mozilla.org/mozilla-central/rev/bcadc378309d
Assignee: nobody → wmccloskey
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
Component: httpd.js → General
You need to log in before you can comment on or make changes to this bug.