Using WinDbg - Hunting Exceptions

re: Using WinDbg - Hunting Exceptions

baal — Sat, 02 Feb 2008 07:44:21 GMT

i have translated your articles to chinese, I am a beginner of .net debugging. My web application has many Performance problems, your articles are so useful to me. but there is not enough info to teach a beginner to solve the trouble. but i will keep studying, follow your articles,keep translating,and learn more.

http://www.cnblogs.com/softfair/category/121611.html

http://www.sula.cn/Default.aspx?cat=9

re: Using WinDbg - Hunting Exceptions

baal — Sat, 02 Feb 2008 08:17:24 GMT

the translated articles not put link back to author,sorry. and typesetting is bad ！^_^

----------------------------------------------------------------------------

re: Using WinDbg - Hunting Exceptions

Hakan Kutluay — Tue, 26 Feb 2008 23:09:43 GMT

Hi Johan,

When i want to run !printexception (!pe), !dumpallexceptions (!dae) commands both i got error like "0:009> !dae No export dae found"

I thought that i correctly configured symbol files and load sos.dll

Thanks,

Hakan

re: Using WinDbg - Hunting Exceptions

Arnold Park — Fri, 29 Aug 2008 07:07:28 GMT

Hi,

can i use the !dae command in .net fx 2.0 environment?

re: Using WinDbg - Hunting Exceptions

JohanS — Thu, 18 Sep 2008 09:20:06 GMT

I'm afraid not. The !dae command is no longer with us in the 2.0 version of sos. Like I say in the post above:

"Unfortunately the !dae command is not available in version 2.0 of sos.dll. Still, it's quite easy to get (more or less) the same result by using the !dumpheap command. If we just type "!dumpheap -type Exception" we'll get a list of all objects with the string "Exception" in their class name. This is almost as good."

re: Using WinDbg - Hunting Exceptions

David McMurray — Thu, 10 Sep 2009 19:17:20 GMT

Hi,

I'm currently trying to debug a .NET Framework 1.1 web application and working my way through all I can find on this, and your articles are certainly helping me to understand how it's done.

But I am having some problems with the commands that apparently should be in the 1.1 version of SOS.dll. I have tried SOS.dll version 1.1.4322.2032 and downloaded and tried 1.1.4322.573 but neither of these have the !printexception/!pe or !dumpallexceptions/!dae commands. Whenever I try to use !pe for example I get 'No export pe found'.

!help only lists the following commands: COMState, ClrStack, DumpClass, DumpDomain, DumpHeap, DumpMD, DumpMT, DumpModule, DumpObj, DumpStack, DumpStackObjects, DumpVC, EEHeap, EEStack, EEVersion, FinalizeQueue, GCInfo, GCRoot, IP2MD, Name2EE, ObjSize, ProcInfo, RWLock, SyncBlk, ThreadPool, Threads, Token2EE and u.

Any ideas why these commands are missing?

Unfortunately my app, that was working perfectly until I put some duplicate code into a separate class, is crashing after some Javascript opens a modal window containing an ASPX page, but before that page runs any code I can debug in Visul Studio 2003. So I'm trying to debug this with WinDbg.

Message External component has thrown an exception.

Source System.Web DEV

TargetSite Void ThrowIfCompilerErrors(System.CodeDom.Compiler.CompilerResults, System.CodeDom.Compiler.CodeDomProvider, System.CodeDom.CodeCompileUnit, System.String, System.String)

StackTrace at System.Web.Compilation.BaseCompiler.ThrowIfCompilerErrors(CompilerResults results, CodeDomProvider codeProvider, CodeCompileUnit sourceData, String sourceFile, String sourceString) at System.Web.Compilation.BaseCompiler.GetCompiledType() at System.Web.UI.PageParser.CompileIntoType() at System.Web.UI.TemplateParser.GetParserCacheItemThroughCompilation()

re: Using WinDbg - Hunting Exceptions

JohanS — Wed, 07 Oct 2009 13:38:34 GMT

Hi David,

Apparently these commands are no longer available for the public version of SOS. An educated guess as to why that is would be that the command depends on information that is no longer available in the public symbols.

You'll have to use the, almost as good; "!dumpheap -type Exception" as described above.

/ Johan