Mail Archives: djgpp/1999/05/19/08:22:48
In article <3742A1A3 DOT 5363151C AT eik DOT bme DOT hu> you wrote:
[...]
> No optimizations were used as sometimes I found them erroneous.
[...]
> The hangup occurs in 'realloc()'. It is usually a page fault.
These two items alone, together with the fact that the problem only
happens with DJGPP 2.02, but not 2.01, strongly suggest that your
program is indeed buggy. It almost certainly writes past the end of
allocated storage, sometimes.
> I seem to remember for something about a change in malloc()'s codes.
> Can it be the cause?
It would not really be the cause of the problem. But there is a
difference in the implementation of malloc() and friends, between
DJGPP 2.02 and 2.01, making it less forgiving to a certain class of
program bugs -- writing to memory outside what you allocated. I.e.,
the real problem would be in your program, but only the new malloc
would experience the crash, as a symptom of it.
You may want to test out 'yamd', Nate Eldredge's 'Yet Another Malloc
Debugger', to find out what exactly happens, or any other malloc
debugging tool for DJGPP.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -