A Very Troubled Application...
Mike Andrews <[email protected]> Tue, 9 Jun 2009 11:06:19 -0500
| Newsgroups | gmane.comp.windows.devel.dotnet.advanced |
|---|---|
| Message-ID | <[email protected]> |
I have a very troubled application (not mine but a 3rd party) that likes to fail with various Unhandled exceptions (memory access and others) when certain files are loaded (I have no idea of the reason). Sometimes loading a file causes a COM exception to occur (no one knows why and it's very unlikely that the manufacturer will ever fix it). This causes the entire application to crash (and/or provide some other unpredictable behavior). This does not occur most of the time but only occasionally. However I must account for these eventualities as this process will be running on multiple servers and I need it the most stable I can get it. What I have been doing is looking for the process in the process list and then killing it. That works most of the time but when one of those dialogs is thrown up asking you to click OK it really messes things up. I've started looking for the dialog, but the time when the dialog appears varies so any predictability is out. What I need to know is if it's possible to attach a hook (or some other such mechanism) to the window to intercept any unhandled win32 exceptions similar to the capability available in the .NET framework. I'm at my wit's end here on this one. I need to create something stable enough so I can recover on the server and continue. Any help or information would be most appreciated. Thanks, Mike =================================== View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives