In the Visual C++ debugger, you can only stop on memory location writes if the data changes. However, the magical new version of WinDBG available at www.microsoft.com/ddk/debugging offers a BA (Break on Access) command that will stop on memory reads. Be prepared to spend some time with WinDBG as it's much harder to use that the Visual Studio debugger.
Dig Deeper on Windows client management
Related Q&A from John Robbins
What is a JAD session? This term is referred to often in job postings and seems like some kind of brainstorm you carry out with a client to define IT... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.