Closed
Bug 801448
Opened 13 years ago
Closed 13 years ago
WARNING: no registered socket provider: file netwerk/base/src/nsSocketTransport2.cpp, line 788
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: posidron, Unassigned)
References
Details
Attachments
(1 file)
15.91 KB,
text/plain
|
Details |
Sockets are not working for me with an optimized (-O1 -g) ASan enabled build.
Everything works fine with a non-opt ASan build though.
This also includes WebSocket support etc:
WARNING: unable to continue without random number generator: file /Users/cdiehl/Code/Mozilla/mc-asan-opt/netwerk/protocol/websocket/WebSocketChannel.cpp, line 2475
Attached console log of NSPR_LOG_MODULES=nsSocketTransport:5
Reporter | ||
Updated•13 years ago
|
Summary: WARNING: unable to continue without random number generator: file netwerk/protocol/websocket/WebSocketChannel.cpp, line 2475 → WARNING: no registered socket provider: file netwerk/base/src/nsSocketTransport2.cpp, line 788
Comment 1•13 years ago
|
||
I don't know what an asan build is, how to make one, or why it matters. help?
Reporter | ||
Comment 2•13 years ago
|
||
ASan is a memory error detector, you can find the instructions here:
https://developer.mozilla.org/en-US/docs/Building_Firefox_with_Address_Sanitizer
decoder is our ASan maintainer he is already CCed.
Comment 3•13 years ago
|
||
I wouldn't know any reason why this should behave differently in an ASan build. I also can't see anything immediately obvious from the log.
Reporter | ||
Comment 4•13 years ago
|
||
-O1 opt debug builds without ASan are working properly but not with ASan enabled.
Comment 5•13 years ago
|
||
See bug 799572. We seem to have found at least one bug in clang. Maybe this is another clang bug.
mcmanus: http://www.chromium.org/developers/testing/addresssanitizer
Our security assurance people (and others) build Firefox with ASAN to find memory corruption bugs (use after free, etc.).
See Also: → 799572
Comment 6•13 years ago
|
||
Good point. Christoph, can you try your build settings without -faddress-sanitizer though? However, OSX builds are always done with Clang, so it must be more than just the fact that Clang is used to compile. Or your version of Clang is different from the one on try :)
Reporter | ||
Comment 7•13 years ago
|
||
I am using clang r161442 for ASan builds and 'Apple clang version 4.0 (tags/Apple/clang-421.0.60) (based on LLVM 3.1svn)' for native builds.
Without -faddress-sanitizer in CXX flags the build runs fine.
Reporter | ||
Updated•13 years ago
|
Whiteboard: [fuzzblocker]
Reporter | ||
Comment 8•13 years ago
|
||
Problem solved, needed to update clang to r164411 and everything works fine.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Whiteboard: [fuzzblocker]
You need to log in
before you can comment on or make changes to this bug.
Description
•