You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Had the same issue, ended up making a QFileSystemWatcher look for a file "/etc/goodbye" to appear and to call QCoreApplication::quit() when this happened.
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.
The text was updated successfully, but these errors were encountered: