Windows Call Stack Crash Dump only shows wow64

Question

Problem

I have a Windows application that we have developed for home use. Thanks to Windows error handling, the window remains open, and I can easily create a crash dump from the task manager.

I used crash-dumps on linux via eclipse before, but this is the first time on Windows.

Equipment

The server is Windows 2012, and my development machine is Windows 7.

Windbg

When I load a crash dump into Windbg, load my characters, and then select, to look at the call stack, the only lists:

How can I see the application call stack specifically?

Answer 1

It looks like your applications are a 32-bit application, and you used 64Bit Taskmgr to dump.

Instead, you should use ProcessExplorer , it takes care of bit :

Process Explorer v15.3: it also creates dump files corresponding to the bit size of the target process

Or, run 32Bit Taskmgr from C:\Windows\SysWOW64 to generate a dump.

Answer 2

As already answered, you took a 64-bit dump of a 32-bit application. There are several options for a 32-bit dump of a 32-bit application on a 64-bit OS , just select the one that is most convenient for you.

If this is the only dump you have, and there is hardly a chance to get a better dump, you can try !sw switch to 32-bit mode:

 0:014> !sw Switched to 32bit mode 0:014:x86> 

Notice how the command prompt has changed. IMHO, the same effect can be achieved using .effmach

 0:014> .effmach x86 Effective machine: x86 compatible (x86) 0:014:x86> 

except that you explicitly specify the mode in which the !sw command switches between the two.

In the case of the .NET application, none of them helped me, since SOS cannot work with dumps of the wrong bit size.