Code review comment for lp:~robertcarr/mir/input-lttng

> > Unfortunately I am unable to make lttng work (with both the existing message
> processor
> > report and my new report) so I haven't been able to confirm the output
>
> Did you follow the instructions in HACKING.md (especially the LD_PRELOAD
> note)?

libmirserverlttng.so no longer seems to be work for me too.

vis:

$ lttng create mirsession -o /tmp/mirsession
Session mirsession created.
Traces will be written in /tmp/mirsession
$ lttng enable-event -u -a
All UST events are enabled in channel channel0
$ lttng start
Tracing started for session mirsession
$ LD_PRELOAD=./lib/libmirserverlttng.so bin/integration-tests
...
[ FAILED ] 13 tests, listed below:
[ FAILED ] SurfaceLoop.creating_a_client_surface_allocates_buffer_swapper_on_server
[ FAILED ] SurfaceLoop.creating_a_client_surface_allocates_buffers_on_server
[ FAILED ] SurfaceLoop.all_created_buffers_are_destoyed
[ FAILED ] SurfaceLoop.all_created_buffers_are_destoyed_if_client_disconnects_without_releasing_surfaces
[ FAILED ] ErrorReporting.c_api_returns_error
[ FAILED ] BespokeDisplayServerTestFixture.display_info_reaches_client
[ FAILED ] BespokeDisplayServerTestFixture.starting_display_server_starts_input_manager
[ FAILED ] SurfaceFirstFrameSync.surface_not_rendered_until_buffer_is_pushed
[ FAILED ] ApplicationMediatorReport.session_connect_called
[ FAILED ] ApplicationMediatorReport.session_create_surface_called
[ FAILED ] ApplicationMediatorReport.session_next_buffer_called
[ FAILED ] ApplicationMediatorReport.session_release_surface_called
[ FAILED ] ApplicationMediatorReport.session_disconnect_called

13 FAILED TESTS