From: Dave Bird Newsgroups: comp.os.msdos.djgpp Subject: Re: Error General Fault Protection on quit??? Date: Sun, 29 Aug 1999 19:07:07 +0100 Organization: ARS HakeMongers inc...... ><_'> <_" Message-ID: <$QodhXALbXy3EwjC@xemu.demon.co.uk> References: <7pvk33$ut4$1 AT nnrp1 DOT deja DOT com> NNTP-Posting-Host: xemu.demon.co.uk X-NNTP-Posting-Host: xemu.demon.co.uk:158.152.196.209 X-Trace: news.demon.co.uk 935955759 nnrp-04:16648 NO-IDENT xemu.demon.co.uk:158.152.196.209 X-Complaints-To: abuse AT demon DOT net MIME-Version: 1.0 X-Newsreader: Turnpike (32) Version 4.01 Lines: 20 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com In article <7pvk33$ut4$1 AT nnrp1 DOT deja DOT com>, Sid writes >I made a bmp loader >it works fine but when the program quit Sid, the textbook suggestion for this is that you are probably deallocating some memory on exit, and have done a dodgy deallocation of a pointer e.g. one which has already been reallocated (or maybe just one which is corrupted). Cure the former case by setting pointers to NULL __immediately__ after deallocating them. I don't know whether it is possible to right a function which tests for an invalid pointer without bombing. You could then call it in key, but rarely visited, gateways such as destructors. -- ^-^-^-@@-^-;-^ http://www.xemu.demon.co.uk/ (..)__u news:alt.smoking.mooses