"Program not being run" errormessage when start debug with F5

When I start debug with F5 key, I got a fake errormessage: "Program not being run" (messagewindow title: "executable failed").
It is just frightening, because program starts normally in a second, and covers small error messagebox.

This message comes up if
-previous debug run ended at "Signal received. Inferior stopped because it received a signal from the os. Signal: SIGSEGV Segmentation fault"
-I click Ok on errormessage
click in QT Debug Abort debugging,
-got a "The gdb process exited unexpectedly (crashed)" message,
-click Ok
-then push F5 for a next try.
the "Program not being run" appears.

I have a sequence of clicking actions in my program that lead to Segment fault error.
If I repeat these steps to segment fault error, then next F5 run displays "Program not being run" error again.
If I don't reach segment fault, instead I exit my program normally (by Windows' top-right red X), next F5 run won't display the error.

I have this weird behaviour for weeks, and it seems to me that this funny message comes up at different runtime errors, not only for "Segment fault"