@Christian-Ehrlicher It took me a whole day, but I finally understood that you were referring to the fact that exit()/quit() can't be used in the same vein as requestInterruption()/isInterruptionRequested() or terminate().

I first learned about basic QThread semantics so long ago (more than a decade I think), that the fact that it's possible to not understand that got completely lost on me.

Also, what backtrace to you get from the debugger ?

He,
If you don't do a real good update now, it will bite you in the ass later on! Count on it!!
Since he stops the running thread, it is a program with an finite loop, not as you mentioned that maya is not totally right. Otherwise check out the QThreadPool stuff for higher level QThread control.

Finally, the best/clean way I found to deal with my requirement was this:

Inside the main.cpp and before I start my service, I make all the verifications I need... if something goes wrong, then I call "return 0;" and that's it, a clean exit. If everything goes well, then I start my service. End of the story.

Thank you for your advices guys! :)

Search the forum for the code... see here

@voidtrance said:

@Rondog Thanks for the advice. I'll look into the closeEvent() method.

The MainWindow::closeEvent() provided exactly what I needed.

@Chris-Kawa, i see what you did there! :d
thanks, didn't even think about that approach before! very useful!