How to crash gracefully

[lni]

Besides, if you fear things such as assert(), then simply do a gracefull error check and recovery instead of asserting.

In a perfect world, we all should be doing that. Unfortunately, no one can write a bug free software. Nobody wants to be hit by a car, it is just the car hits people

Anyway, I have a crash test, if anyone fix or solve a problem, please include in this thread so we all get benefit of it.

[wysota]

In a perfect world, we all should be doing that. Unfortunately, no one can write a bug free software. Nobody wants to be hit by a car, it is just the car hits people

Does it matter if instead of assert() you call myAssert()? Especially that AFAIR it's a macro anyway...

void myAssert(bool t){
  if(t) return;
  QMessageBox::critical(0, "Assert", "An assert has occured, the application will close");
  abort();
}

void myAssert(bool t){
  if(t) return;
  QMessageBox::critical(0, "Assert", "An assert has occured, the application will close");
  abort();
}

To copy to clipboard, switch view to plain text mode 

[rbp]

If you want to be able to issue a full report from your application, there is a simple way to do it. Start your application as a child process of another application that will act as a feedback manager. The parent can monitor the state of the child and when it terminates, it can read its stderr (that can contain a backtrace) and can send the data to the producer or do a number of different things.

I tried this suggested method with QProcess and was able to catch the crash. However the Windows crash dialog also came up, which would be confusing for the user.
Do you know how to make Windows leave me alone? Do I need to suppress signals like SIGABRT?
Alternatively maybe I could try and access the Windows crash data...

Sorry that this question is moving out of Qt territory and into C++/Windows programming. If you think it's too off topic I could reask it in a more relevant forum.
I'm usually a Linux programmer so this kind of stuff is particularly frustrating!