Comments on: Crash Dump Analysis Patterns (Part 17) https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Thu, 07 May 2026 13:54:19 +0000 http://wordpress.org/?v=2.3.3 By: Software Generalist » Blog Archive » Reading Notebook: 25-November-09 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-174973 Software Generalist » Blog Archive » Reading Notebook: 25-November-09 Tue, 10 Aug 2010 17:29:39 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-174973 [...] .load vs. .loadby (pp. 8 - 11) - Some additional load scenarios for legacy SOS and its server version can be found in comments to Managed Code Exception pattern: http://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/ [...] […] .load vs. .loadby (pp. 8 - 11) - Some additional load scenarios for legacy SOS and its server version can be found in comments to Managed Code Exception pattern: http://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/ […]

]]> By: Crash Dump Analysis » Blog Archive » Icons for Memory Dump Analysis Patterns (Part 33) https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-150279 Crash Dump Analysis » Blog Archive » Icons for Memory Dump Analysis Patterns (Part 33) Thu, 06 May 2010 16:01:06 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-150279 [...] Today we introduce an icon for Managed Code Exception pattern: [...] […] Today we introduce an icon for Managed Code Exception pattern: […]

]]> By: Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 95) https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-108316 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 95) Mon, 07 Dec 2009 17:03:37 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-108316 [...] cases where we don’t see managed code exceptions or managed stack traces by default, we need to identify CLR threads in order to try various SOS [...] […] cases where we don’t see managed code exceptions or managed stack traces by default, we need to identify CLR threads in order to try various SOS […]

]]> By: Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 93) https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-106142 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 93) Tue, 24 Nov 2009 16:52:28 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-106142 [...] specific SOS extension. For example, x64 WinDbg is not able to analyze the managed stack for a managed code exception in 32-bit [...] […] specific SOS extension. For example, x64 WinDbg is not able to analyze the managed stack for a managed code exception in 32-bit […]

]]> By: Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 90) https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-101152 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 90) Wed, 28 Oct 2009 11:31:24 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-101152 [...] we have a managed code exception that was enveloping a handled unmanaged code exception, Mixed (Nested) [...] […] we have a managed code exception that was enveloping a handled unmanaged code exception, Mixed (Nested) […]

]]> By: Software Generalist » Blog Archive » Reading Notebook: 15-July-09 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-84823 Software Generalist » Blog Archive » Reading Notebook: 15-July-09 Wed, 15 Jul 2009 18:15:38 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-84823 [...] kernel32.dll, for example (Windows API DLL). For some examples from crash dumps see patterns: Managed Code Exception or JIT [...] […] kernel32.dll, for example (Windows API DLL). For some examples from crash dumps see patterns: Managed Code Exception or JIT […]

]]> By: Kusum https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-77427 Kusum Tue, 02 Jun 2009 17:22:45 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-77427 Very useful! Thanks. Very useful! Thanks.

]]> By: Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 77) https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-47795 Crash Dump Analysis » Blog Archive » Crash Dump Analysis Patterns (Part 77) Tue, 21 Oct 2008 10:31:42 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-47795 [...] simple pattern I planned to write about long time ago. It is called C++ Exception. It is similar to Managed Code Exception and can manifested by the same RaiseException call on top of the stack (red). However it is [...] […] simple pattern I planned to write about long time ago. It is called C++ Exception. It is similar to Managed Code Exception and can manifested by the same RaiseException call on top of the stack (red). However it is […]

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-10218 Dmitry Vostokov Thu, 08 Nov 2007 13:08:16 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-10218 The current version of WinDbg 6.8.4.0 and !analyze -v command show both native and managed stack traces from .NET 64-bit application memory dump so there is no need to load SOS manually The current version of WinDbg 6.8.4.0 and !analyze -v command show both native and managed stack traces from .NET 64-bit application memory dump so there is no need to load SOS manually

]]> By: Dmitry Vostokov https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-8185 Dmitry Vostokov Wed, 10 Oct 2007 17:35:37 +0000 https://www.dumpanalysis.org/blog/index.php/2007/07/20/crash-dump-analysis-patterns-part-17/#comment-8185 For some crash dumps we get the following message saying that sos.dll cannot be found: 0:000> .loadby sos mscorwks The call to LoadLibrary(C:\WIN_NO_SP\Microsoft.NET \Framework\v2.0.50727\sos) failed, Win32 error 0n126 "The specified module could not be found." Please check your debugger configuration and/or network access Here we need to check where Microsoft.NET\Framework\v2.0.50727\sos.dll is installed on our crash dump analysis host and use .load command: 0:000> .load C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\sos.dll For some crash dumps we get the following message saying that sos.dll cannot be found:

0:000> .loadby sos mscorwks
The call to LoadLibrary(C:\WIN_NO_SP\Microsoft.NET \Framework\v2.0.50727\sos) failed, Win32 error 0n126
“The specified module could not be found.”
Please check your debugger configuration and/or network access

Here we need to check where

Microsoft.NET\Framework\v2.0.50727\sos.dll

is installed on our crash dump analysis host and use .load command:

0:000> .load C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\sos.dll

]]>