On Sun, 2020-12-06 at 23:06 +0100, Phil wrote:
> Hope you are not calling any functions that are not "async-safe" in
> that signal handler.
> Looks like l_main_quit just sets a flag so is probably ok, but what
> is to stop l_info interrupting another log call?
I went ahead and CC'd the list so everyone can see it.
Thats a good point. What is unclear to me is if the actual signal
handler call is from an interrupt or not. Looks like the l_signal APIs
use an IO read handler and are a bit more complex than e.g. calling the
Not that it makes it 'ok' but every single example/tool, even IWD,
prints from the signal handler. If this is an issue we certainly would
want to remove those prints.
Does anyone else know the details of this? Are signal handlers
registered from l_main_run_with_signal printf safe?