This is an archive of the discontinued LLVM Phabricator instance.

Change Socket::Read / Socket::Write to log to LOG_COMMUNICATION instead of LOG_HOST
ClosedPublic

Authored by jasonmolenda on Jul 24 2015, 3:18 PM.

Details

Summary

I'm adding some new host logging to help diagnose problems of finding executable files or dSYMs, Greg suggested we should add it to the Host log channel. Currently Socket::Read and Socket::Write are logging to Host which is super verbose. He suggests that we should switch these over the Communication log channel instead. Some of Socket.cpp is logging to LOG_CONNECTION already. Zachary, any opinion on this? I think you touched this most recently. Not sure if you're using this logging yourself.

Diff Detail

Repository
rL LLVM

Event Timeline

jasonmolenda retitled this revision from to Change Socket::Read / Socket::Write to log to LOG_COMMUNICATION instead of LOG_HOST.
jasonmolenda updated this object.
jasonmolenda added a reviewer: zturner.
jasonmolenda set the repository for this revision to rL LLVM.
jasonmolenda added a subscriber: lldb-commits.
zturner edited edge metadata.Jul 24 2015, 3:20 PM
zturner added a subscriber: zturner.

Seems reasonable. lgtm

jasonmolenda accepted this revision.Jul 24 2015, 3:42 PM
jasonmolenda added a reviewer: jasonmolenda.
This revision is now accepted and ready to land.Jul 24 2015, 3:42 PM
jasonmolenda closed this revision.Jul 24 2015, 3:42 PM

Sending source/Host/common/Socket.cpp
Transmitting file data .
Committed revision 243175.