Search in Google for: "How to set up for capturing Heap Corruption in a process dumping at the point it occurs " it explains not only how to enable page heap, but also how to obtain dump.
This is hardly a "demo"--it's command line instructions on how to enable the debug feature but doesn't take you any further than that. A couple sentences would have sufficed and certainly an instructional video isn't needed.
I feel you did not take us far enough. Where do we find the trace file? And how do we use it to find the root cause of the heap corruption?
Search in Google for: "How to set up for capturing Heap Corruption in a process dumping at the point it occurs
" it explains not only how to enable page heap, but also how to obtain dump.
Very good, so does the proc-dump gather this info when the process crashes?
Where we can find the trace and how to analyze it
Page guards are NO_ACCESS, not READ_ONLY
This is hardly a "demo"--it's command line instructions on how to enable the debug feature but doesn't take you any further than that. A couple sentences would have sufficed and certainly an instructional video isn't needed.
Bullshit..no real debugging..misleading title