Print expected/actual thread names when running EventBase logic in unexpected thread
authorGiuseppe Ottaviano <ott@fb.com>
Wed, 21 Jun 2017 19:28:52 +0000 (12:28 -0700)
committerFacebook Github Bot <facebook-github-bot@users.noreply.github.com>
Wed, 21 Jun 2017 19:35:32 +0000 (12:35 -0700)
commitfc84e02a134e25cb8f417f8f9d8629e00bfb48e7
tree72bd2e50dc527be0b24e39049ae9a225c21a6d59
parent15884e47719c8b4e5f3c5ea51f50aebb46887611
Print expected/actual thread names when running EventBase logic in unexpected thread

Summary: The existing assertion errors do not give a lot of information to track down which thread is incorrectly using the `EventBase`. Print both the current thread name and the name of the thread running the event base loop.

Reviewed By: luciang

Differential Revision: D5289790

fbshipit-source-id: 563c7f68b7f9b7a6e85e22290d7e81afbf89871e
folly/io/async/AsyncSSLSocket.cpp
folly/io/async/AsyncServerSocket.cpp
folly/io/async/AsyncServerSocket.h
folly/io/async/AsyncSocket.cpp
folly/io/async/AsyncUDPSocket.cpp
folly/io/async/EventBase.cpp
folly/io/async/EventBase.h
folly/io/async/EventBaseLocal.cpp
folly/io/async/EventHandler.cpp
folly/io/async/NotificationQueue.h
folly/io/async/VirtualEventBase.h