> >> >> 2) When using windows remote desktop client, weston exits after >> accepting connection due to SIGPIPE signal. Here's backtrace: >> ==31717== >> ==31717== Process terminating with default action of signal 13 (SIGPIPE) >> ==31717== at 0x6080AD0: __write_nocancel (syscall-template.S:81) >> ==31717== by 0x6A3C156: freerds_send_stream (compositor-freerds.c:130) >> ==31717== by 0x6A3C4A4: freerds_refresh_region >> (compositor-freerds.c:186) >> ==31717== by 0x6A3DA19: freerds_treat_message >> (compositor-freerds.c:821) >> ==31717== by 0x6A3DF0A: freerds_client_activity >> (compositor-freerds.c:920) >> ==31717== by 0x4E3D7F7: wl_event_source_fd_dispatch (event-loop.c:86) >> ==31717== by 0x4E3E1A8: wl_event_loop_dispatch (event-loop.c:421) >> ==31717== by 0x4E3BFEC: wl_display_run (wayland-server.c:961) >> ==31717== by 0x411C3F: main (compositor.c:4242) >> >> I can provide more detailed logs, if anyone is interested. >> > > Yes please send them. > I uploaded them here: https://github.com/mceier/weston-logs These are complete logs from valgrind and gdb, for 4 different tests. Tests have (very) short description in README.
> Regards, thanks for testing and the feedback. > > -- > David FORT > website: http://www.hardening-consulting.com/ _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
