|
|
Fredrik Eriksson wrote:
>>> Nowadays, actually, they tend to play with the memory map to cause
>>> traps to occur where you want to see things. Breakpoint when you
>>> write a variable? Map the page the variable is in as read-only, then
>>> when the trap happens, see if the instruction was pointing to the
>>> variable.
>>
>> Interesting. I thought (in C) all variables exist on the machine stack?
>
> Not true, but even so, the stack is still memory.
Well true - but my point was more that the stack gets touched every 3
instructions or so, and setting traps on it would light up the system
like a festive season tree. ;-)
Post a reply to this message
|
|