Changes between Version 8 and Version 9 of AppDebugWin

Timestamp:

Aug 7, 2008, 6:13:54 AM (16 years ago)

Author:

romw

Comment:

--

AppDebugWin

@@ -231 +231 @@
 Starting with Visual Studio 2005, Microsoft re-vamped the whole C Runtime Library.  Part of the re-vamp process was to do parameter checking on each function.  Places that would normally return a NULL value now cause a structured exception to be thrown.
 
-The nature of this structured exception is different than most as they specifically coded it so that it will not engage the BOINC Runtime Debugger and it'll display a dialog box asking the user if they wish to debug the error. If the user cancels the error code 0xc000000d is returned without any more information.
-
-To get more information with this error you'll need to create a function like this:
-
-{{{
-#ifdef _WIN32
-void AppInvalidParameterHandler(const wchar_t* expression, const wchar_t* function, const wchar_t* file, unsigned int line,     uintptr_t pReserved ) {
-        fprintf(
-                stderr,
-                "Invalid parameter detected in function %s. File: %s Line: %d\n",
-                function,
-                file,
-                line
-        );
-        fprintf(
-                stderr,
-                "Expression: %s\n",
-                expression
-        );
-        // Cause a Debug Breakpoint.
-        DebugBreak();
-}
-#endif
-}}}
-
-The following code block should be added after the call to boinc_diagnostics_init():
-
-{{{
-#ifdef _WIN32
-        // Every once and awhile something looks at a std::vector or some other
-        // CRT/STL construct that throws an exception when an invalid parameter
-        // is detected.  In this case we should dump whatever information we 
-        // can and then bail.  When we bail we should dump as much data as 
-        // possible.
-        _set_invalid_parameter_handler(AppInvalidParameterHandler);
-#endif
-}}}
-
 When this issues happens in the future it'll describe which CRT function call was passed an invalid parameter and it should dump out the callstack for all threads.
-
-The function blocks above overwrite the default behavior of the CRT when an invalid  parameter is detected.
 
 === Privileged Instruction (0xc0000096) ===