From:	Bernhard Stiftner <stiftnersoftwareNOstSPAM AT gmx DOT at DOT invalid>
Subject:	DLX+Allegro+PDMLWP = "dangerous" mixture???
Newsgroups:	comp.os.msdos.djgpp
Message-ID:	<0a0bc822.c304c00f@usw-ex0108-062.remarq.com>
Lines:	24
Bytes:	972
X-Originating-Host:	195.3.96.211
Organization:	http://www.remarq.com: The World's Usenet/Discussions Start Here
X-Wren-Trace:	eAYjCwoTVB5VVQYHBVIJCgYGGQUXFUcCBioOCBdcHlJJUR9SRhVdUVxJUFJZ
Date:	Mon, 14 Aug 2000 10:57:21 -0700
NNTP-Posting-Host:	10.0.2.62
X-Complaints-To:	wrenabuse AT remarq DOT com
X-Trace:	WReNphoon3 966277764 10.0.2.62 (Mon, 14 Aug 2000 11:29:24 PDT)
NNTP-Posting-Date:	Mon, 14 Aug 2000 11:29:24 PDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,
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).
The interesting/funny thing: it only happens SOMETIMES and
in graphics mode - but a small test like
for(i=0; i<100; i++) {
  test=malloc(256);
  free(test);
  }
works however.
Strange thing...
So, am I getting crazy, is it my PC or are that just some
incompatibilities???
Btw, has anybody experienced similar things?


* Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping.  Smart is Beautiful

- Raw text -