Mir

Comment 12 for bug 1506358

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

And again from:

==3839== Process terminating with default action of signal 6 (SIGABRT)
==3839== at 0x6EB8418: raise (raise.c:54)
==3839== by 0x6EBA019: abort (abort.c:89)
==3839== by 0x7DE184C: __gnu_cxx::__verbose_terminate_handler() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==3839== by 0x7DDF6B5: ??? (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==3839== by 0x7DDF700: std::terminate() (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==3839== by 0x7DDF968: __cxa_rethrow (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==3839== by 0x52C1821: ??? (in /usr/lib/x86_64-linux-gnu/libmirclient.so.9)
==3839== by 0x52C6F36: ??? (in /usr/lib/x86_64-linux-gnu/libmirclient.so.9)
==3839== by 0x52C0280: mir_buffer_stream_release (in /usr/lib/x86_64-linux-gnu/libmirclient.so.9)
==3839== by 0x52C030C: mir_buffer_stream_release_sync (in /usr/lib/x86_64-linux-gnu/libmirclient.so.9)
==3839== by 0x43A737: xmir_unrealize_cursor (xmir-cursor.c:83)
==3839== by 0x55A1A0: FreeCursor (cursor.c:124)