title: Q_ASSERT has different behavior when my project is built in Visual Studio vs. Qt Creator
body: <p>This seems to be a bug, because on Qt Creator, Q_ASSERT(false) causes my application to quit even though the documentation says it should allow you to break at the assertion:</p>
  
  <blockquote>
    <p>On Windows, for debug builds, this function will report a _CRT_ERROR
    enabling you to connect a debugger to the application.</p>
  </blockquote>
  
  <h2>On Qt Creator:</h2>
  
  <p>When compiling my project in Qt Creator+MinGW, the code <code>Q_ASSERT(false);</code> causes the program to display this message (screenshot below), after which the application quits:</p>
  
  <blockquote>
    <p>This application has requested the Runtime to terminate it in an
    unusual way. Please contact the application's support team for more
    information.</p>
  </blockquote>
  
  <p><img src="https://i.stack.imgur.com/xASjm.png" alt="enter image description here"></p>
  
  <p>and Application Output pane shows this debug output:</p>
  
  <pre><code>ASSERT: "false" in file ..\IntegrateWithQt\main.cpp, line 6
  Invalid parameter passed to C runtime function.
  Invalid parameter passed to C runtime function.
  </code></pre>
  
  <h2>On Visual Studio:</h2>
  
  <p>When compiling the same project using Visual Studio (I import it with the Qt Addin), I get a much more useful Abort/Retry/Ignore dialog, where clicking Retry breaks the program at the location of the assert:</p>
  
  <p><img src="https://i.stack.imgur.com/ZYjLV.png" alt="enter image description here"></p>
  
  <p>The version of Qt I link to both in Qt Creator and in Visual Studio is 4.8.1. Both projects are built in Debug mode.</p>
  
  <p>So how do I get Qt Creator to allow me to break at the line of the assertion in debug mode?</p>