1. Register Creator for post-mortem debugging.
2. Run an application built with MSVC2010.
3. Crash the application.
4. In the appearing dialogs, click the options that will start Creator for debugging the application.
   Creator starts and presents an error message:
   

With Creator 3.1, this used to work.

It seems that the root cause is that Creator tries to start gdb. AFAIK, post-mortem debugging with gdb on Windows never worked. In addition, I don't see a reason why a crashed MSVC-application should be debugged using gdb. CDB was correctly autodetected by Creator.