If the server dies, clients sometimes display "Caught exception at Mir/EGL driver boundary: ... std::exception::what: Failed to send message to server: Broken pipe"

This happens because the server disconnection is detected while in a driver callback (e.g. a call from the driver to get the next buffer). I don't think we can avoid this, unless we don't log the boundary exceptions at all, or perphaps only ignore this particular exception?

It's just a user interface issue really. Especially if we're already cleaning up correctly, no exception text should be spewed to the client's stderr/out.

there's a log here, in this duplicate bug 1383696
marking rtm14 likewise

description from the other bug to repro

"When opening an application I sometimes get an app that never opens, on launch ps shows the whole group (oxide) as being suspended and there's this error in the log"

unduping the other bug since this is talking about the error logging rather than a cause

The problem's now a bit worse since r2194:

Signal 1 received. Good night.
Caught exception at Mir/EGL driver boundary: /home/dan/bzr/mir/managed-surface/src/client/rpc/stream_socket_transport.cpp(166): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"
[1420515827.256161] (EE) MirSurfaceAPI: Caught exception at client library boundary (in mir_surface_release): Failed to send message to server: Broken pipe
[1420515827.256314] (EE) MirConnectionAPI: Caught exception at client library boundary (in release): Failed to send message to server: Broken pipe

So we need to remove the old exception message first. Second we shouldn't be logging anything because "Broken pipe" isn't really an error. The same information is already conveyed to the client app by SIGHUP.

Still happening in Mir release 0.11.0:

Signal 1 received. Good night.
[1423635409.524339] <ERROR> MirSurfaceAPI: Caught exception at client library boundary (in mir_surface_release): /build/buildd/mir-0.11.0+15.04.20150209.1/src/client/rpc/stream_socket_transport.cpp(154): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"
[1423635409.524508] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in release): /build/buildd/mir-0.11.0+15.04.20150209.1/src/client/rpc/stream_socket_transport.cpp(154): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorEEEEE
std::exception::what: Failed to send message to server: Broken pipe
32, "Broken pipe"

See also bug 1312099.

Syncing task from Mir.