weston: add wait-for-debugger option
authorPekka Paalanen <pekka.paalanen@collabora.co.uk>
Wed, 1 Nov 2017 08:26:46 +0000 (10:26 +0200)
committerPekka Paalanen <pekka.paalanen@collabora.co.uk>
Tue, 28 Nov 2017 07:17:24 +0000 (09:17 +0200)
commit1fdeb68013ae3c716e32dadbf9269027836ff732
tree18bf2f6baba9fb0c9574fe13c6dd9e9c60f76612
parent3baf9ce7e80da5fc15dbc7b413f99081f344aaa9
weston: add wait-for-debugger option

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 <pekka.paalanen@collabora.co.uk>
Acked-by: Daniel Stone <daniels@collabora.com>
Reviewed-by: Quentin Glidic <sardemff7+git@sardemff7.net>
Reviewed-by: Ian Ray <ian.ray@ge.com>
compositor/main.c
man/weston.ini.man
man/weston.man