Article View: comp.os.ms-windows.programmer.memory
Article #4Re: What *is* a General Protection Fault
From: Solution Technology
Date: Mon, 25 Sep 1995 19:40
Date: Mon, 25 Sep 1995 19:40
17 lines
1215 bytes
1215 bytes
David Preece (dmpreece@tcp.co.uk) 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? : 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. That usually indicates uninitialized pointers or data. The debugger frequently supplies a zero initial value while non-debug running uses the previous contents of memory. Ken Walter
Technical Details
Message-ID:
<4470k6$147l@navajo.gate.net>Path:
arc1-ca.pugleaf.net!news.gate.net!not-for-mailReferences:
<446uh6$ieu@zeus.tcp.co.uk>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!news.gate.net!not-for-mail From: stidev@news.gate.net (Solution Technology) Newsgroups: comp.os.ms-windows.programmer.memory,comp.os.ms-windows.programmer.tools.mfc,comp.lang.c++ Subject: Re: What *is* a General Protection Fault Followup-To: comp.os.ms-windows.programmer.memory,comp.os.ms-windows.programmer.tools.mfc,comp.lang.c++ Date: 25 Sep 1995 15:40:54 -0400 Message-ID: <4470k6$147l@navajo.gate.net> References: <446uh6$ieu@zeus.tcp.co.uk> NNTP-Posting-Host: navajo.gate.net X-Newsreader: TIN [version 1.2 PL2]