Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a bool variable which should be true, but is sometimes set to false. I have set a memory breakpoint to see what is changing that. To my surprise, the breakpoint did not hit, but the variable went to false again.
What could change the memory without memory breakpoint catching it?
A few thoughts.
If you pass the bool value into a kernel function and THAT is changing it (or perhaps a kernel function call is overwriting memory because it is called incorrectly) then that won’t fire a data breakpoint.
If you are using multiple processes and another process, that isn’t being debugged, writes to that memory location then you the breakpoint won’t get triggered.
(Edit) As pointed out in the comments a DMA into the memory the hardware breakpoint is on will also not get picked up.
My guess is that you aren’t checking a buffer size appropriately somewhere and you are getting hit by (1), perhaps when reading data from a file?