Orchid XP v7 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?

Dunno. Often, the static variables (i.e., those with a lifetime that 
matches the process) are allocated, well, statically. Whether it's part 
of the stack that never gets popped or not isn't too relevant.

Anyway, so? The machine stack is in memory-mapped memory too, yes?

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?

Post a reply to this message