remdynamic
July 13th, 2013, 19:42
Hi!
When I have a certain byte or range of bytes of which I know it will contain certain interesting data at some point, I usually set a hardware breakpoint on it.
However, I noticed that it doesn't always break. For example, now I want to keep an eye on the byte at DS:[9F2020], so I set a hardware BP there. However
(EAX = 9F2020)
MOV DWORD PTR DS:[EAX],EBP
won't cause Olly to break. However
(EDI = 9F2024)
REP STOS DWORD PTR ES:[EDI]
will cause Olly to break.
Am I misinterpreting the adressing system in Olly? I assume that
009F2020 | 00 00
__________^this is the byte on 009F2020
Do I need just to set my breakpoint a byte or 4 bytes before that?
When I have a certain byte or range of bytes of which I know it will contain certain interesting data at some point, I usually set a hardware breakpoint on it.
However, I noticed that it doesn't always break. For example, now I want to keep an eye on the byte at DS:[9F2020], so I set a hardware BP there. However
(EAX = 9F2020)
MOV DWORD PTR DS:[EAX],EBP
won't cause Olly to break. However
(EDI = 9F2024)
REP STOS DWORD PTR ES:[EDI]
will cause Olly to break.
Am I misinterpreting the adressing system in Olly? I assume that
009F2020 | 00 00
__________^this is the byte on 009F2020
Do I need just to set my breakpoint a byte or 4 bytes before that?