From: Bernhard Stiftner Subject: Re: DLX+Allegro+PDMLWP = "dangerous" mixture??? Newsgroups: comp.os.msdos.djgpp Message-ID: <06889872.53b4ce9e@usw-ex0109-068.remarq.com> Lines: 20 Bytes: 896 X-Originating-Host: 195.3.96.210 Organization: http://www.remarq.com: The World's Usenet/Discussions Start Here References: <0a0bc822 DOT c304c00f AT usw-ex0108-062 DOT remarq DOT com> <1659-Tue15Aug2000091619+0300-eliz AT is DOT elta DOT co DOT il> X-Wren-Trace: eJC1nZyFwojDw5CRk8SfnJCQj5OBg9GUkLyYnoHKiMTfx4nE0IPLx8rfxsTO Date: Thu, 17 Aug 2000 13:22:09 -0700 NNTP-Posting-Host: 10.0.2.68 X-Complaints-To: wrenabuse AT remarq DOT com X-Trace: WReNphoon3 966545288 10.0.2.68 (Thu, 17 Aug 2000 13:48:08 PDT) NNTP-Posting-Date: Thu, 17 Aug 2000 13:48:08 PDT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > Does the same program work correctly if you link it statically, without DLX? Yes, perfectly - absolutely&100% free of bugs&crashes. In the DLX version, I have now removed the INI processing from a loop and changed dynamically allocated strings (char*) to constant ones (char[256]) and it works better now. But this can't be the final solution - this is just cheating around the problem. The interesting thing is that "free" does not necessarily crash - I can call it hundreds of times in a test loop without having problems, but some functions which call "free" fail SOMETIMES (like LIBINI's "ini_free") and some even ALWAYS (like Allegro's "draw_trans_sprite"). I can't explain this behaviour with logical thinking... * Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is Beautiful