crash-dumps

问题 I´m facing a huge problem since a couple weeks. I´ve an asp.net application hosted under IIS7 (W2008 SP1), and every a couple hours it starts consuming near 50% of the CPU when maybe there're no users connected. It´s understandable since we are using Quartz.net to make some application recicling, but we could not reproduce the problem yet. Here is a trace made with JetBrains dotTrace 3.1 while the CPU was high: http://mycenter.info/tmp/DotTraceSnapshot.zip Usually the process wasting CPU is

问题 Crash logs used to be accessible through the Settings app. I can't find that in iOS 8. Where did that go? It's not gone now is it. 回答1: I found it. It moved, it's no longer inside General/Diagnostics... It's in Privacy/Diagnostics. 回答2: Start by opening up the Settings app. Navigate to Settings - Privacy - Diagnostics & usage - Diagnostics & usage Data Tap on the crash and you will see a text field with a crash log. Long press to Select All and then Copy the crash text. Paste it into

问题 I have a crash dump from production to identify a memory leak. When I used DebugDiag (v2 update 2), I get a report DebugDiag did not detect LeakTrack.dll loaded in w3wp.DMP, so no leak analysis was performed on this file. If you are troubleshooting a memory leak, please ensure LeakTrack.dll is injected into the target process using the DebugDiag tool before or generating new dumps . I'm not able to find a way to inject LeakTrack.dll from DebugDiag UI or after going through the documentation.

问题 I have an application running as service. The application crashes time to time. The application is written in vb.net and runs its tasks at new thread (one at time). I have collected crash dumps and started analyzing. From analyze of log file created by the application (analysis of dump supports it) it seems that a crash occurs when no task is running and application is waiting for a next System.Timers.Timer event. First I loaded a .dmp file to VS2010: Process Architecture: x86 Exception Code:

问题 I downloaded symbols for windows2003 server from here http://msdn.microsoft.com/en-us/windows/hardware/gg463028 I did what is described here - http://blogs.msdn.com/b/johan/archive/2007/11/13/getting-started-with-windbg-part-i.aspx. But when I try to run !threadpool it says 0:024> !threadpool Failed to load data access DLL, 0x80004005 Verify that 1) you have a recent build of the debugger (6.2.14 or newer) 2) the file mscordacwks.dll that matches your version of mscorwks.dll is in the version

问题 Platform is Windows 7 SP1. I recently spent some time debugging an issue that was caused because a code was passing an invalid parameter to one of the "safe" CRT functions. As a result my application was aborted right away with no warning or anything -- not even a crash dialog. At first, I tried to figure this out by attaching Windbg to my application. However when the crash happened, by the time the code broke into Windbg pretty much every thread had been killed save for ONE thread on which

问题 I'm trying to diagnose a crash issue for a .NET 4 application. The last time it crashes in a user's machine, Windows Error Reporting doesn't gather the mini dump of the application. I've check the DumpFolder in registry, and I can find the dump files for old crashes, but there's just no new dump file for the last one. The event log of the crash says: Application: MyApp.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error int the .NET Runtime at IP

问题 I am developing a Windows Phone 8.1 app. I want to add a functionality that whenever the app crashes a memory dump is captured and written to a log . I want to know if there is any way to log the crash dump while the user is using the app on his phone and it crashes. I found this question which is similar to mine but is for Windows 8 . It says that we can use the 'Application_UnhandledException' method in App.xaml.cs to obtain the dump. But is this method supported in Windows Phone 8.1 too

问题 I've got a crash minidump to analyze. My program is multithread Qt5 application. I'm not a debugging guru but usualy I can easily find place where program failed, but this time I can't. I opened dump file in Visual Studio 2010, clicked "Debug with native only" and it shows me where problem is: it is thread with location "__CxxUnhandledExceptionFilter". Call stack is like this: msvcr100.dll()!_abort() msvcr100.dll()!terminate() program.exe!__CxxUnhandledExceptionFilter(_EXCEPTION_POINTERS *

问题 I am using Windbg to load a crash dump from managed code (C#, a console application built for Any CPU), and crash dump is created on x64 platform. I am debugging on x64 platform. I have using the following command to load private symbol of my application. Here are what the commands I am using in Windbg. (set symbol path and copy FooService.pdb pdb file to local symbol path D:\Debug) 0:016> .reload /f .*** WARNING: Unable to verify checksum for FooService.exe DBGHELP: FooService.pdb- private