From: "Michael Stewart" <mike AT reggin DOT freeserve DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Wierd Memory Problems
Date: Mon, 12 Jul 1999 09:39:09 +0100
Organization: (Posted via) Netcom Internet Ltd.
Message-ID: <7mc9hk$sng$1@taliesin.netcom.net.uk>
References: <19990711224517 DOT 20554 DOT 00004047 AT ng-ff1 DOT aol DOT com>
NNTP-Posting-Host: hgty.capgemini.co.uk
X-Trace: taliesin.netcom.net.uk 931768692 29424 194.42.240.2 (12 Jul 1999 08:38:12 GMT)
X-Complaints-To: abuse AT corp DOT netcom DOT net DOT uk
NNTP-Posting-Date: 12 Jul 1999 08:38:12 GMT
X-Newsreader: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Lines: 34
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Da Phire wrote in message <19990711224517 DOT 20554 DOT 00004047 AT ng-ff1 DOT aol 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.

Sounds like you try and reference some unallocated memory. Post a code
sample that demonstrates the problem.