From: daphire AT aol DOT com (Da Phire)
Newsgroups: comp.os.msdos.djgpp
Subject: Wierd Memory Problems
Lines: 16
NNTP-Posting-Host: ladder06.news.aol.com
X-Admin: news AT aol DOT com
Date: 12 Jul 1999 02:45:17 GMT
Organization: AOL http://www.aol.com
Message-ID: <19990711224517.20554.00004047@ng-ff1.aol.com>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I've been getting some rather wierd problems with my program that seem to have
something to do with memory. At first, there seemed to e some kind of problem
when I used certain variables that had been declared and initialized properly,
and I found that changing the order in which the variables were declared would
sometimes help (the error I would get is SIGSEGV, which I know is a
memory-related error). After performing several workarounds, the problem came
to rest on one of my reallocs, so now I always get the memory error I
programmed in rather than SIGSEGV. Seeing this, I tried all the documented
methods for increasing available RAM in the FAQ (and even in windows help - I
have Win98), none of which worked. Just as a test, I decided to try cutting off
a huge chunk of one of the bitmaps I was loading into the program, realizing
that if it was a memory problem, that would clear it up, or at least allow the
program to advance a bit further until it hit the memory ceiling. But it did
absolutely nothing - which is what totally baffels me. Does anybody know what
could be causing this? I think my program hits somewhere around 1MB (give or
take) when it crashes.