🚀 go-pugleaf

On 25 Sep 1995, David Preece wrote:

> ..I was always under the impression that a GPF was Windoze's way
> of stopping one application from writing over anothers' memory.
> Am I right?
> 

From what I know, the answer is "sort of". 'Doze *detects* such 
violations but does not necessarily stop them. It then kills the 
offending program by way of a GPF (after the damage has been done). 
That's why 'Doze tends to be unstable after GPFs.

> And if so, why is this happening:
>   
>   I am allocating a very complex dialog box on the heap. When compiled
>   with Visual C++ in debug mode, it executes fine. When compiled in 
>   release mode (with the compiler and linker options otherwise identical)
>   this dialog box GPF's.

There is probably a bug in there. Sometimes seg. violations go 
undetected, since even though a program is writing to the wrong part of 
memory, it may still own that memory. However, when you eliminate the 
extra debugging code, the program may end up straying outside its bounds. 
Look for stray pointers and the like.

- Trung