Home/ Questions/Q 60025
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T18:05:50+00:00

I have an MFC application compiled with /clr and I’m trying to implement a

  • 0

I have an MFC application compiled with /clr and I’m trying to implement a final handler for otherwise un-caught managed exceptions. For native exceptions, overriding CWinApp::ProcessWndProcException works.

The two events suggested in Jeff’s CodeProject article,Application.ThreadException and AppDomain.CurrentDomain.UnhandledException, are not raised.

Can anyone suggest a way to provide a final managed exception handler for a mixed executable?

Update:

It appears that these exception handlers are only triggered downstream of Application.Run or similar (there’s a worker thread flavor, can’t remember the name.) If you want to truly globally catch a managed exception you do need to install an SEH filter. You’re not going to get a System.Exception and if you want a callstack you’re going to have to roll your own walker.

In an MSDN forum question on this topic it was suggested to override a sufficiently low-level point of the main MFC thread in a try ... catch (Exception^). For instance, CWinApp::Run. This may be a good solution but I haven’t looked at any perf or stability implications. You’ll get a chance to log with a call stack before you bail and you can avoid the default windows unahndled exception behavior.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Taking a look around the internets, you’ll find that you need to install a filter to get the unmanaged exceptions passing the filters on their way to your AppDomain. From CLR and Unhandled Exception Filters:

    The CLR relies on the SEH unhandled exception filter mechanism to catch unhandled exceptions.

    • 0