Date: Tue, 15 Aug 2000 09:16:19 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp AT delorie DOT com Message-Id: <1659-Tue15Aug2000091619+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b In-reply-to: <0a0bc822.c304c00f@usw-ex0108-062.remarq.com> (message from Bernhard Stiftner on Mon, 14 Aug 2000 10:57:21 -0700) Subject: Re: DLX+Allegro+PDMLWP = "dangerous" mixture??? References: <0a0bc822 DOT c304c00f AT usw-ex0108-062 DOT remarq DOT com> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Bernhard Stiftner > Newsgroups: comp.os.msdos.djgpp > Date: Mon, 14 Aug 2000 10:57:21 -0700 > > I'm experiencing strange problems when using DLX, Allegro, > PDMLWP and LIBINI (this nice lib for Windoze-like INI- > files). PDMLWP and LIBINI are linked with the DLX loader > (the EXE file), Allegro is linked with the DLX, importing > the lib functions from the EXE. When this DLX calls "free" > directly or indirectly (as "ini_free" does, for example), > it leads to a nice GPF ("attacking" some Windoze modules > (like VMOUSE) or generating a GPF in RMCB when its run > under pure DOS). Does the same program work correctly if you link it statically, without DLX?