Mail Archives: djgpp/1999/07/12/05:36:25
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.
- Raw text -