SOS does not support the current target architecture

c# .net-4.0 windbg dump freeze
Justin Pihony picture Justin Pihony · May 7, 2013 · Viewed 12.8k times · Source

I am trying to use windbg to research a hang dump file created on an x64 machine for our x86 process. This is a 4.0 x86 application, so just to get an unmanaged stack, I had to do the following:

.loadby sos clr
.load wow64exts
!sw
kL

However, everytime I try to get the managed stack via !clrstack I get the error in the title. What am I missing?

Answer

trydis picture trydis · May 7, 2013

I believe you will have to use the 32-bit task manager, located in C:\Windows\SysWOW64\taskmgr.exe to get a 32-bit dump.

More info here: http://blogs.msdn.com/b/tess/archive/2010/09/29/capturing-memory-dumps-for-32-bit-processes-on-an-x64-machine.aspx

Related questions

How to debug corruption in the managed heap

My program throws an error which it cannot handle by a catch(Exception e) block and then it crashes: Access Violation Corrupted State Exception. This is the weird thing, because, as I know, corrupted state exceptions are thrown from unmanaged …

Read More
What is the best way to implement a "timer"?

What is the best way to implement a timer? A code sample would be great! For this question, "best" is defined as most reliable (least number of misfires) and precise. If I specify an interval of 15 seconds, I want the …

Read More
An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode

I Installed DotNetOpenAuth SDK-3.4.5.10201.vsix and I can't get it working. It works locally (when I run as localhost) but when i try to publish it ain't working. The IIS error message I get is Error Summary HTTP Error 500.22 - …

Read More