Mir

The exception thrown by clients when a server dies is more confusing and worrying than it should be - what(): Failed to send message to server: Bad file descriptor

Bug #1312099 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
Low
Unassigned
mir (Ubuntu)
Triaged
Low
Unassigned

Bug Description

The exception thrown by clients when a server dies is more confusing and worrying than it should be -

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what(): Failed to send message to server: Bad file descriptor

It sounds like a catastrophic client bug. Actually it just means the server went away. So maybe we should change the error message to explain that and sound less worrying.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Hmm, actually I thought clients weren't meant to emit any exceptions at all?

Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

Changed in mir (Ubuntu):
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.