Jim Blandy 28ebe45d1b Bug 899757: Make nsServerSocket::InitWithAddress provide more detailed error results. r=mayhemer, r=ted ... I looked through the NSPR socket creation functions that InitWithAddress uses to see which errors they could return, and placed appropriate comments in ErrorAccordingToNSPR. The test coverage is not great; in particular, I wasn't able to find a way to elicit "address in use" errors from Windows (although I could from Linux); the web says that Windows is much more relaxed about binding listening sockets than Unix derivatives. I'm interested in suggestions.		2013-09-06 08:06:22 -07:00
..
crashtests	Back out e46601eb7279:533dc9ea3301 (bug 912322) for Android reftest bustage	2013-09-04 21:49:16 -07:00
idl	Bug 899367 - Stop storing the window proxy on the JSContext. r=mccr8	2013-09-04 14:06:56 -07:00
loader	Bug 912293 - Remove now redundant boilerplate from Makefile.in. r=gps	2013-09-05 09:01:46 +09:00
public	Bug 905017 (part 3, attempt 2) - Move profiling stack stuff from jsapi.h to js/ProfilingStack.h. r=billm.	2013-08-19 23:45:26 -07:00
shell	Bug 912293 - Remove now redundant boilerplate from Makefile.in. r=gps	2013-09-05 09:01:46 +09:00
src	Bug 899757: Make nsServerSocket::InitWithAddress provide more detailed error results. r=mayhemer, r=ted	2013-09-06 08:06:22 -07:00
tests	Back out e46601eb7279:533dc9ea3301 (bug 912322) for Android reftest bustage	2013-09-04 21:49:16 -07:00
wrappers	Bug 912411 (part 2) - Move JSID_{VOID,EMPTY}HANDLE from jsapi.{h,cpp} to Id.{h,cpp}. r=luke.	2013-09-05 16:08:57 -07:00
moz.build