From: Patrick <pat...@gm...> - 2008-08-11 16:42:03
|
I have a C# program with a p\invoke call that triggers a heap error. I am trying to catch and log this error. The weird thing is, when I run my program in Visual Studio 2008 in Debug mode (F5), I can catch the error - first a breakpoint is triggered, then Visual Studio informs me I have an access violation corruption of the heap, then I am given the option to stop or continue, I continue and then I hit my breakpoint which is in a catch(AccessViolation aex) { log(aex.Message) } However, if I publish my solution and run it, I know that I still have a corruption of the heap, but my catch exception is not executed and there is nothing logged. I would really like to log this message -- my goal is to use swig to find and log errors in our code, and i would love to be able to log corruptions of the heap. Thanks for any ideas. Patrick |