On 01/11/2017, 16.24, "wayland-devel on behalf of Pekka Paalanen" <[email protected] on behalf of [email protected]> wrote: > > From: Pekka Paalanen <[email protected]> > > When you need to start Weston via weston-launch, systemd unit, or any > other runner, it is annoying to try to get in with a debugger, > especially if the thing you are interested in happens at start-up. To > make it easy, a new option is introduced. > > The new option, implemented both as a command line option and a > weston.ini option, raises SIGSTOP early in the start-up, before the > weston_compositor has been created. This allows one to attach a debugger > at a known point in execution, and resume execution with SIGCONT. > > Signed-off-by: Pekka Paalanen <[email protected]>
Reviewed-by: Ian Ray <[email protected]> _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
