Mail Archives: djgpp-workers/1999/06/08/05:36:18
On Mon, 7 Jun 1999, Eric Rudd wrote:
> The biggest problem I've had is a propensity for gcc to crash on
> systems which use HIMEM.SYS but not EMM386 or Windows. The
> symptoms, which occur on about 1% of the compilations, are a bomb in
> an RMCB with a traceback. The keyboard then invariably locks up,
> necessitating a hard re-boot, though the disk cache continues to
> commit normally after the lock-up.
FWIW, I have never seen such problems (but then I never use HIMEM-only
systems long enough to see a 1%-chance problems).
> I have observed this problem on several computers. Oddly enough, my
> own DJGPP-compiled apps have never had this problem.
Are the compiler binaries old by any chance? If they were built with
old versions of DJGPP, then this might be due to a problem whereby if
the compiler crashed, it would leave some exception handlers pointing
to void, because the abnormal exit code bypassed the function that
restored the old handlers.
Another source of such problems may be if you run Make which invokes
some raw COFF image (via go32-v2). Versions of go32-v2 before v2.02
didn't restore the interrupt handlers at exit (because the execution
thread never got back to go32-v2's own code once it launched the child
program), so if you press a key at a wrong moment, you could have
crashes that manifest themselves as Page Faults in RMCB.
> I don't know what I can do to diagnose the problem, other than to
> manually transcribe the traceback.
Please post at least one case of this with the traceback and any
other relevant information.
- Raw text -