Comments
3 comments
-
I have the same issue, can you please give any idea?
-
I'm sorry, I don't remember exactly what I did at the time. The linked issue in the EDIT above has a bit more information, about using corflags to set the process to 32 bit. Hope that helps.
-
using corflags all works, if I can suggest it should be more usable having one more executable for 32bit dump management...
Add comment
Please sign in to leave a comment.
https://forum.red-gate.com/discussion/86625/this-process-is-64-bit-but-this-memory-dump-is-not-memory-dumps-can-only-be-read-if-they-are-the-s#latest
Trying to open a memory dump of a 32-bit process running on a 64-bit OS, using AMP running on a 64-bit machine. I get the message:
This process is 64-bit, but this memory dump is not. Memory dumps can only be read if they are the same bitness as the process.
I assume by "this process" it means ANTS, and not the process we're taking the dump from. Is there a way to run AMP in a 32-bit mode then? The doco here: Analyzing memory dumps - ANTS Memory Profiler 11 - Product Documentation (red-gate.com) says:
Memory dumps of 32-bit applications can only be opened when running AMP in a 32-bit environment.
I tried launching the GUI from a 32-bit cmd process, but it was unimpressed.