sijk / qt-unix-signals Goto Github PK

When using QCoreApplication in main() as suggested in example.cc, the code works fine.
But if i change QCoreApplication to QApplication (as i am using UI), unix signals are not raised.

The application works fine on Desktop.
The above issue is with Embedded Linux.

I see that QT internally blocked the signals SIGINT, SIGTERM to route it to socket. (using signalfd()).

can i call sigprocmask with SIG_UNBLOCK in my handler to emit the signal.
(If i do it signal is emitted successfully)

Will there be any side-effects on QT Application if i set it directly.

Thanks for a great piece of code!
There is only couple of problems:

1. You seem to forget to copy the sa_flags=0 initialization from the Qt example.
   In my case it leads to not restoring the handler after the first call, time to time.
2. I am not sure why did Qt people use sigemptyset in the original example.
   Possibly, they wanted to add the signals later with sigaddset, but forgot about it.
   Anyway, now your handler is not protected from any signal to arrive during its
   execution. I doubt it's the desired effect.

I thought it would be useful to add support for projects build with CMake.
This will result in an easy and automated way to include qt-unix-signal into your own QT project build with CMake.
I will make a PR today and link it as an answer to this issue.