From: rpolzer AT web DOT de (Rudolf Polzer) Newsgroups: comp.os.msdos.djgpp Subject: Re: Windows ME and DJGPP References: <20010120205730 DOT 25849 DOT 00000491 AT ng-fd1 DOT aol DOT com> <3a6b7917 DOT 10793503 AT news DOT sci DOT fi> <3A6CB71F DOT 8B4E86C9 AT phekda DOT freeserve DOT co DOT uk> <94k3dc$lf9$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <94pm3k$1qf$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <94rrk4$sro$1 AT antares DOT lu DOT erisoft DOT se> X-newsgroup: comp.os.msdos.djgpp X-realname: Martin Stromberg X-Mailer: GehtDichNenScheissdreckAn 1.0 Message-ID: User-Agent: slrn/0.9.6.2 (Linux) Date: Fri, 26 Jan 2001 22:30:30 +0100 Lines: 16 NNTP-Posting-Host: 213.7.27.6 X-Trace: 980544252 news.freenet.de 7183 213.7.27.6 X-Complaints-To: abuse AT freenet DOT de To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Martin Stromberg schrieb folgenden Unsinn: > Rudolf Polzer (rpolzer AT web DOT de) wrote: > : The only memory allocation problems that really can occur in C++ are NULL > : pointers (caught by the processor => SIGSEGV) and memory leaks (then you > > That (getting SIGSEGV) won't work on WINDOZE if I'm not mistaken. Why > don't you try it and see for yourself?... My selfwritten REBOUNCE level editor always crashes on exit (after saving) with a SIGSEGV and I do not know (probably I am freeing a bitmap twice) why, but RHIDE always crashes after that so I cannot debug it. But from this I know that SIGSEGV can also be caught on Windoze. -- Nuper erat medicus, nunc est vispillo, Diaulus: Quod vispillo facit, fecerat et medicus.