https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/ Structural and Behavioral Patterns for Software Diagnostics, Forensics and Prognostics Tue, 05 May 2026 13:57:40 +0000 http://wordpress.org/?v=2.3.3 https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/#comment-104982 Nariman Tue, 17 Nov 2009 13:32:26 +0000 https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/#comment-104982 Yes, using the latest: WinDbg, 64-bit SOS, 64-bit MSCORWKS, 64-bit SOSEX, Symbol Path http://msdl.microsoft.com/download/symbol; the configuration is correct, so we suspected issues with the public symbols, but it turns out a simple .reload is the cure (apparently, it's required once). Yes, using the latest: WinDbg, 64-bit SOS, 64-bit MSCORWKS, 64-bit SOSEX, Symbol Path http://msdl.microsoft.com/download/symbol; the configuration is correct, so we suspected issues with the public symbols, but it turns out a simple .reload is the cure (apparently, it’s required once).

]]> https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/#comment-104872 Dmitry Vostokov Mon, 16 Nov 2009 23:22:57 +0000 https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/#comment-104872 Are you using the latest WinDbg? I check tomorrow with W2K8 64-bit and let you know. I had some problems with 64-bit !teb but don't remember with which OS version Are you using the latest WinDbg? I check tomorrow with W2K8 64-bit and let you know. I had some problems with 64-bit !teb but don’t remember with which OS version

]]> https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/#comment-104839 Nariman Mon, 16 Nov 2009 20:27:58 +0000 https://www.dumpanalysis.org/blog/index.php/2009/05/11/raw-stack-dump-of-all-threads-part-3/#comment-104839 After moving to 64-bit Windows 2008 (IIS7), we've started receiving the same output for !address and !teb (ntdll.pdb size is 2,157,568 - and only is found in the symbol folder). Most commands that don't rely on this symbol seem to be working. Is there a workaround that will allow us to continue using these commands as opposed to having to hand-write scripts with specific offsets? After moving to 64-bit Windows 2008 (IIS7), we’ve started receiving the same output for !address and !teb (ntdll.pdb size is 2,157,568 - and only is found in the symbol folder). Most commands that don’t rely on this symbol seem to be working. Is there a workaround that will allow us to continue using these commands as opposed to having to hand-write scripts with specific offsets?

]]>