Full page heap settings on x64 Windows
Sponsored link: Memory Dump Analysis Services
Debugging Experts Magazine Online
If we want to use gflags.exe to enable page heap settings (or any other image file execution options) for a 32-bit executable running on x64 Windows we should use 32-bit version of gflags.exe from 32-bit Debugging Tools for Windows (see windbg.org for quick download links) or if we want to set appropriate registry key manually we should use Wow6432Node branch:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\<process name with .exe extension>
Name: GlobalFlag
Type: REG_DWORD
Value: 0x02000000
Name: PageHeapFlags
Type: REG_DWORD
Value: 0x00000003
- Dmitry Vostokov @ DumpAnalysis.org -
_1125.png)
Museum of Debugging and Memory Dumps
7/7/2010 - 8/8/2010 Annual Competition: Tell Your Windows Debugging Story
Crash and Hang Analysis Audit Service
CARE: Crash Analysis Report Environment
Crash Dump and Software Trace Analysis Training and Seminars
Access OpenTask Titles on Safari Books Online
DATA (Dump Analysis + Trace Analysis) Facebook group
Please join the community of memory (dump) and trace analysis engineers. This group promotes scientific methods and memory dump-based worldview.
Twitter @ DumpAnalysis You can now follow portal and blog news at DumpAnalysis on Twitter
LinkedIn Group Dr. Watson Enthusiasts All about Dr. Watson errors and more. Get news, excerpts and progress reports about the forthcoming book The Science of Dr. Watson: An Illustrated History of Debugging (ISBN 978-1906717070)
2010 (0x7DA) - The Year of Dump Analysis 2011 (0x7DB) - 2020 (0x7E4) The Debugging Decade
International Memory Analysts and Debuggers Day: 07.07 and/or 08.08 starting from The Year of Dump Analysis, 2010, 7DA
AnnouncementsComing Soon:
Management Bits: An Anthology from Reductionist Manager
Debugging Notebook: Essential Concepts, WinDbg Commands and Tools
Crash Dump Analysis for System Administrators and Support Engineers
New Magazines:
Debugged! MZ/PE: MagaZine for/from Practicing Engineers
New Books:
Memory Dump Analysis Anthology: Color Supplement for Volumes 1-3
Memory Dump Analysis Anthology, Volume 3
First Fault Software Problem Solving: A Guide for Engineers, Managers and Users
x64 Windows Debugging: Practical Foundations
Also available:
Windows Debugging: Practical Foundations
DLL List Landscape: The Art from Computer Memory Space
Dumps, Bugs and Debugging Forensics: The Adventures of Dr. Debugalov
WinDbg: A Reference Poster and Learning Cards
Memory Dump Analysis Anthology, Volume 2
Memory Dump Analysis Anthology, Volume 1
New Children's Book:
July 10th, 2009 at 5:18 am
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\…
This is actually a wrong way of doing that. You need to use either 32bit version of gflags.exe just like you have mentioned or 32bit version of regedit/reg without Wow6432Node in the path. Try it in Windows 7 x64 and you will see the difference.
July 10th, 2009 at 5:20 am
> Try it in Windows 7 x64 and you will see the difference.
(After thinking for 2 seconds) Actually, no, you will not. There is a symbolic link between those two on Windows 7. Anyway 32bit regedit/reg is the way to go.
July 10th, 2009 at 10:39 am
Agree. I personally prefer gflags.exe and use regedit to double check
July 12th, 2010 at 8:23 pm
Related question: How can you confirm from a user provided full memory dump that full pageheap has been enabled vs pageheap lite? !gflag only shows if +hpa was enabled (0×02000000) and more specificly I am interested in what values for PageHeapFlags (e.g. 0×1003) and VerifyFlags (e.g. 1) options may have been set to prior to the dump. TIA.