debugdiag

问题 I am using the DebugDiag to analyze a crash dump on windows. This is the report summary description: In XXXX.dmp the assembly instruction at msvcr120!abort+4a in C:\Windows\System32\msvcr120.dll from Microsoft Corporation has caused an unknown exception (0x40000015) on thread 26 And the call stack is: ntdll!NtWaitForMultipleObjects+a KERNELBASE!WaitForMultipleObjectsEx+e8 kernel32!WaitForMultipleObjectsExImplementation+b3 kernel32!WerpReportFaultInternal+215 kernel32!WerpReportFault+77

问题 I am using DebugDiag Analysis tool in the server to generate report for the dump file which is 1.74 GB and it's running for more than a day and could not generate report. I also tried running the tool in separate computer (local) https://www.iis.net/learn/troubleshoot/performance-issues/troubleshooting-high-cpu-in-an-iis-7x-application-pool It stops on "Preloading symbol files (this may take a while)" 来源： https://stackoverflow.com/questions/56782704/debugdiag-analysis-is-taking-too-long-to

问题 I'm trying to run DebugDiag Analysis (v2.3) on my Windows 10 laptop using crash-dump files generated from a w3wp.exe process on a Windows Server 2016 box... but the application never passes "Dumping Thread Data" (the progress animation continues, so it's not a GUI hang.) (I am not allowed to installed DebugDiag on the server, as it is production box and owned by a client. They allowed me to change the registry settings to generate the crash-dump files, which I then copied to my local machine.

问题 I'm trying to run DebugDiag Analysis (v2.3) on my Windows 10 laptop using crash-dump files generated from a w3wp.exe process on a Windows Server 2016 box... but the application never passes "Dumping Thread Data" (the progress animation continues, so it's not a GUI hang.) (I am not allowed to installed DebugDiag on the server, as it is production box and owned by a client. They allowed me to change the registry settings to generate the crash-dump files, which I then copied to my local machine.

问题 I just experienced a high CPU issue on our production aserver and decided to practice debugging such situations locally to be prepared for this in the future, but when I try to debug a local MVC4 site, I dont get the same informative stack trace as the tutorial does. Question: Does anyone know if it is possible to get a more informative stack trace? I would expect to see HomeController.Index somewhere but the only method call I see is: System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion

问题 Probably this is a normal situation, but I am confused. I am running my C# Debug application from Visual Studio. DebugDiag is set up to attach to the process automatically. I have a rule to collect crash dumps from this application, and the rule defines that the action for unconfigured first chance exceptions should be "none". But when the application crashes, and when I look at the dump files it says that there is a first chance exception. From the answer to this SO question, I understand

问题 The scenario is pretty simple: I have a memory leak in a Windows Store App, identified as native after using dotMemory profiler. Since this tool is limited to analyzing managed memory I did further research by performing a memory dump analysis using DebugDiag. This got me one step further and I could find that the increasing memory is committed to a heap used by mscoreei (anyone has additional info about this dll? A simple google search does not return much) DebugDiag also has a nice feature

问题 We've been encountering an issue with a particular website hosted in iis for which I've not managed to get much information from the event log. I'm a bit out of my league with these low level 'raw' diagnostic tools and I'm not if I'm barking up the wrong tree (in which case please tell me - e.g IIS is just broken) or whether I'm following the correct paths to try and locate the issue. A process serving application pool 'MyWebsite' suffered a fatal communication error with the Windows Process

问题 Recently, my asp.net application crashed. I got the event logs on windows, two type exception message: Application: w3wp.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF9CFDDE3 (000007FEF9B00000) with exit code 80131506. Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2 Faulting module name: clr.dll, version: 4.0.30319.1008, time stamp: 0x517a18ff Exception code: 0xc0000005

问题 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.