From: "Greg Holdridge" <greg AT holdridge7 DOT freeserve DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: A mysterious event
Date: Sun, 13 Aug 2000 17:25:26 +0100
Organization: Customer of Energis Squared
Lines: 26
Message-ID: <8n6i6g$8cn$1@newsg4.svr.pol.co.uk>
NNTP-Posting-Host: modem-69.dernhelm.dialup.pol.co.uk
X-Trace: newsg4.svr.pol.co.uk 966183952 8599 62.136.154.69 (13 Aug 2000 16:25:52 GMT)
NNTP-Posting-Date: 13 Aug 2000 16:25:52 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I have an assembly function (NASM compiled) called _V_SetMode which takes
one parameter - mode number - for modes 320x200 320x240 320x400 or 360x480.
Anyway, I think something is wrong with it because the following occurs...
using the test code as follows:

// position A
_V_SetMode(4);
// position B
while(!kbhit())
{
   // Plot random pixels
}
V_TextMode();

No problems occur and I get random pixels.  If I insert a call to malloc()
at position B, no problem occurs.  However, a call to malloc() at position A
causes my monitor to switch onto power saving until a key is pressed.  What
sort of problem might there be with the code which would flare up following
this sort of change? malloc() is the only action which appears to cause the
issue.

Any help appreciated,

Greg