Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

Flood of exception warnings: Is there any way to disable this?



  • Working in QtCreator 4.7.1, using the MSVC 2015 toolset 140. I upgraded from an older version but if now I am running my application in the debugger, I receive a "flood" of exception warnings of the style:

    Exception at 0x7ffdbe2fa388, code: 0xe06d7363: C++ exception, flags=0x1 (execution cannot be continued) (first chance) at...

    Looking at the location it is quite "normal" C++ code where an exception is thrown in a try{} clause and properly caught further down - nothing to worry about in any case. Also in release mode nothing happens, and when I was still using older versions of QtCreator I also did not get these warnings.

    The bad thing is that I get so many of them that they are hiding the real issues, so I would like to disable them.

    Is there any way to do this? It's quite annoying!


  • Qt Champions 2017

    I have seen this with the native QFileDialog. Honestly I have never figured out why I had got those messages, but as far as I remember I thought it's a thing that comes from the VC runtime. I'd try with mingw just to be sure ...
    Sorry I couldn't be more helpful, but perhaps someone else might have a better idea.



  • I am pretty sure it comes from the debugger - which is from the MS Visual Studio toolkit! I think I do not need to recompile the entire thing with mingw only to find this confirmed: It would take me probably several days with all the related modules...

    Anyway, I could imagine to either have some "switch" to shut up the debugger (including a trick how to apply it from inside the QtCreator), or some option in the QtCreator itself that filters these messages out.

    Actually I did not only switch from an earlier version of QtCreator to now 4.7.1, but also from MSVC 2013 to 2015 at the same time, so the problem could come from the one or the other. (And you are right: chances are high that it is actually the MSVC 2015 debugger...)


Log in to reply