minidump | 易学教程

Capturing R6025 pure virtual call

阅读更多关于 Capturing R6025 pure virtual call

问题 I currently capture MiniDumps of unhandled exceptions using SetUnhandledExceptionFilter however at times I am getting "R6025: pure virtual function". I understand how a pure virtual function call happens I am just wondering if it is possible to capture them so I can create a MiniDump at that point. 回答1: If you want to catch all crashes you have to do more than just: SetUnhandledExceptionFilter I would also set the abort handler, the purecall handler, unexpected, terminate, and invalid

What to do with “The version of SOS does not match the version of CLR you are debugging” in WinDbg?

阅读更多关于 What to do with “The version of SOS does not match the version of CLR you are debugging” in WinDbg?

I'm having a problem with some of my apps. It's a wcf-based app running under IIS6 in Windows 2003 Server (x86): In Event Log I get such an error from "W3SVC-WP" source (EventID=2262): ISAPI 'C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'. I'm trying figuring out what's going on. I've set up creating dump for Orphan Worker Process as described in this KB . When an deadlock occured a minidump is created. Then I take this minidump to try to understand what's happened. Here's I'm stuck. I run WinDbg x86,

Why don't Minidumps give good call stacks?

阅读更多关于 Why don't Minidumps give good call stacks?

问题 I've used minidumps on many game projects over the years and they seem to have about a 50% chance of having a valid call stack. What can I do to make them have better call stacks? I've tried putting the latest dbghelp.dll in the exe directory. That seems to help some. Is Visual Studio 2008 or 2010 any better? (I'm still on VS 2005). The code I use looks like this sample. 回答1: One thing you can do to improve the accuracy of call stacks found in dumps is to use a debugger other than Visual

How do I get at the exception information when using MiniDumpWriteDump out-of-process?

阅读更多关于 How do I get at the exception information when using MiniDumpWriteDump out-of-process?

问题 When using the MiniDumpWriteDump function to create a core dump of a process on Windows, it is recommended (e.g. here, and here) that the MiniDumpWriteDump is run from another "watchdog" process because it may well not work when called from within the same process. At the moment, our application is calling it in-process on an unhandled exception (we do it from a watchdog thread). Since we sometimes have problems with it not working, we'd like to move it to a separate process. Now, signalling

What to do with “The version of SOS does not match the version of CLR you are debugging” in WinDbg?

阅读更多关于 What to do with “The version of SOS does not match the version of CLR you are debugging” in WinDbg?

问题 I'm having a problem with some of my apps. It's a wcf-based app running under IIS6 in Windows 2003 Server (x86): In Event Log I get such an error from "W3SVC-WP" source (EventID=2262): ISAPI 'C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'. I'm trying figuring out what's going on. I've set up creating dump for Orphan Worker Process as described in this KB. When an deadlock occured a minidump is created.

How to create minidump for my process when it crashes?

阅读更多关于 How to create minidump for my process when it crashes?

I am not able to create minidump form my process by changing system setting. So my Question is : Will the system create a minidump for a user process when it crashes If yes, which setting do I need to configure Or do I have to create minidump programmatically. How effective are minidumps while investigating a crash I'm using Windows XP, C++, VC6 You need to programatically create a minidump (with one exception, see next link). CodeProject has a nice article on MiniDumps . Basically, you want to use dbghelp.dll , and use the function MiniDumpWriteDump() (see MSDN on MiniDumpWriteDump ). How

How do I take a good crash dump for .NET?

阅读更多关于 How do I take a good crash dump for .NET?

问题 I have captured a crash dump of my 32 bit .NET application running on a 64 bit Windows operating system. During the analysis somebody found out that I have a 64 bit dump and told me that it is not possible to analyze this dump due to wrong bitness. When using Windows Task Manager to create the dump, I was not aware that I was doing something wrong. This always worked for 32 bit operating systems. How can I take a good dump for .NET, especially with the correct bitness? 回答1: Why is bitness