clipka wrote:

> BTW, in C you can actually peek & poke around as you like on virtually all
> platforms, simply by assigning an arbitrary integer value to a pointer and then
> accessing the memory location pointed to.

I didn't know that, if I ever did, I had forgotten it. Thanks :)
> 
> May result in the application getting terminated for an access violation though,
> courtesy of Intel's "protected mode" and paging mechanisms, which can be used to
> automatically trigger a hardware interrupt when certain memory address ranges
> are accessed, so that the OS can take over and handle the access accordingly
> (killing a misbehaving program, swapping virtual memory back in, or the like).
> 

I blamed those "access violations" that occasionally show up on Windows. So
their really due to a "safety" feature in Intel's hardware. Is that why 
machines with
AMD processor's (reportedly) crash and hangup less frequently?

David :)

Post a reply to this message