summaryrefslogtreecommitdiffstats
path: root/src/ivi-compositor.h
diff options
context:
space:
mode:
authorMarius Vlad <marius.vlad@collabora.com>2022-09-21 17:29:39 +0300
committerMarius Vlad <marius.vlad@collabora.com>2022-09-23 18:15:11 +0300
commit897449688a9c7f934d45acd1eaa09d766d6da67a (patch)
treeeca05f5812ced7baa8cb18e8296f8c917dffe391 /src/ivi-compositor.h
parente8761762fcd03d3f561c0a0b761d609ded41c8c3 (diff)
compositor: Use sigaction to trap SIGINT
signalfd interacts badly with gdb's signal trapping - when hitting ctrl-c in a debugger attached to weston, weston will receive the signal. This results in weston exiting cleanly when the intent was to use gdb to interfere with its operation. Trapping SIGINT was introduced in commit 50dc6989 which ensured we would call wl_display_terminate() on SIGINT or SIGTERM to clean up our socket. Killing weston with SIGINT is quite common for several developers, so it's important to preserve this clean shutdown behaviour, so we can't naively stop trapping SIGINT entirely. Instead, use the sigaction() function to trap SIGINT, and have the SIGINT handler send weston SIGUSR2 (SIGUSR1 is already used by xwayland). SIGUSR2 can be trapped in the proper wayland way via wl_event_loop_add_signal(). This way we can properly break our event loop and clean up on SIGINT, but we can also have gdb intercept SIGINT. There are other ways around this, but I'm hoping this one allows people to continue using ctrl-c to stop weston, and doesn't require additional project specific gdb knowledge. Bug-AGL: SPEC-4570 Signed-off-by: Derek Foreman <derek.foreman@collabora.com> Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Change-Id: I42fc186296856861c8b6aee54a302c7c0574a88d
Diffstat (limited to 'src/ivi-compositor.h')
0 files changed, 0 insertions, 0 deletions