3

When debugging a native win32 application, certain unhandled exceptions (more specifically a failed assertion in Windows atlcomcli.h) causes the "unhandled exception" dialog (where you can abort, continue (to debug the exception in visual studio) or ignore) to freeze and be unresponsive - none of the buttons can be pressed.

This means I cannot get the callstack among other things, I have to force-terminate Visual Studio and so I cant get any help on debugging where it crashes.

It works just fine with most other unhandled exceptions that are thrown.

Why is this?

jww
  • 97,681
  • 90
  • 411
  • 885
KaiserJohaan
  • 9,028
  • 20
  • 112
  • 199
  • It would be helpful to have some code that could reproduce the issue. – Steve Aug 25 '16 at 22:54
  • Have you witnessed this on multiple computers? Particular OS? Visual Studio version? – Steve Aug 25 '16 at 22:55
  • 1
    Have you tried putting a breakpoint in the Windows code right before it opens the dialog box? – Keith M Aug 25 '16 at 22:55
  • Have you tried navigating the assertion dialog using the keyboard? Particularly inside drag-and-drop implementations it's not uncommon for debug assertion dialogs to not receive any mouse input. – IInspectable Aug 25 '16 at 23:06
  • Windows 10, VS2015. The actual assertion happens outside my code, in the microsoft headers. I did try with keyboard, still unresponsive. I am mainly looking to see if anyone else encountered similiar issues. – KaiserJohaan Aug 25 '16 at 23:21
  • 1
    Again, others would probably be very willing to try this exact thing, if you could write a very small program that made the proper calls. [Short, Self Contained, Correct (Compilable), Example](http://sscce.org/) – Steve Aug 25 '16 at 23:29
  • The assertion message also appears in the Output window during debugging. You could view the output window, maybe it contains much more helpful error messages. – Jack Zhai Aug 26 '16 at 12:24

1 Answers1

0

One workaround is that you could collect the minidump file for the crashed/freeze issue, debug the crashed dump file and find more helpful information for it:

How can I disable the debug assertion dialog on Windows?

Community
  • 1
  • 1
Jack Zhai
  • 6,230
  • 1
  • 12
  • 20