0

In Windows Error Reporting, I have several dump files for a certain hang. When I open the dump, I get an ugly message

Debugging a 64-bit dump of a 32-bit process requires full heap information. Please collect a 32-bit dump of a 32-bit process.

How can I configure WER to collect and upload the correct dump?

PS: This particular crash happens only on Windows 7 x64. Is there something special about the wow64 emulator on this OS?

AndreiM
  • 815
  • 9
  • 17
  • At the time I have researched it [for this answer](http://stackoverflow.com/questions/24874027/how-do-i-take-a-good-crash-dump-for-net), LocalDumps created bitness aware dumps. – Thomas Weller Jul 26 '16 at 20:24
  • *"When I open the dump"* - What tool are you using to inspect the minidump? Not all debuggers provide the same features when it comes to post-mortem debugging (with WinDbg often being the tool of choice). – IInspectable Oct 10 '16 at 15:27
  • @IInspectable: I use both VS and windbg. – AndreiM Oct 11 '16 at 09:15

1 Answers1

0

You can try setting the DumpType = 2 if you are using local crash dumps. These settings are in the registry under 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

This configures the OS to produce a full crash dump. I'm not 100% sure this will help you though.

See https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx for more information on local crash dumps (user-mode dumps).

This SO post seems related: Debugging dump of 32-bit process captured on 64-bit machine

Also see these blogs: https://blogs.msdn.microsoft.com/amb/2011/05/12/do-not-collect-32bit-process-dumps-with-64bit-task-manager/ https://rhauert.wordpress.com/tag/debugging/

I hope some of these can help you.

Community
  • 1
  • 1
PerryC
  • 1,233
  • 2
  • 12
  • 28