delorie.com/archives/browse.cgi | search |
From: | "A. Sinan Unur" <asu1 AT cornell DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Help! Confused by problems with VESA programming. |
Date: | Tue, 08 Jul 1997 09:53:27 -0400 |
Organization: | Cornell University |
Lines: | 18 |
Sender: | asu1 AT cornell DOT edu (Verified) |
Message-ID: | <33C24657.4AF6@cornell.edu> |
References: | <5psfn0$mpi$1 AT pulp DOT ucs DOT ualberta DOT ca> |
NNTP-Posting-Host: | 128 |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Jon Martin wrote: > > int main(void) > { > VBE_VgaInfo vgainfo; > VBE_ModeInfo modeinfo; > unsigned char colour; > int done = 0; > int y; > unsigned char virtscreen[307200]; i haven't checked the rest of the code but this probably is the culprit. the default stack size for djgpp programs is 256K. you are asking for about 300K. you could stubedit this to 1 Mb and see if it makes a difference. however, a better programming practice would be to allocate the memory for the virtual screen from the heap (using malloc). -- Sinan
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |