Mail Archives: djgpp/1998/02/25/08:46:10
Nate Eldredge (eldredge AT ap DOT net) writes:
> Yes it is.
>
> Weird, irreproducible problems like this are often the sign of some kind of
> hardware failure. The first thing that comes to mind is bad memory. I'd
> suggest testing it somehow (maybe someone will follow up and recommend a
> tester), and replacing it if there is a problem. You might want to back up
> your data in the meantime.
A tester? He probably already has one, in his BIOS. Nearly all computers
I've seen (especially with 32 megs of the stuff) do a memory test at
bootup, of the RAM, CPU caches, and sometimes video memory also.
Other possibilities include:
* Virus infecting the EXEs. (DJGPP apps seem allergic to viruses, probably
because of the stub and COFF image architecture. Infected DJGPP apps
invariably misbehave, often with the Not COFF message.)
Try a virus scan or three.
* Bad disk sector and subsequent corruption of gcc.exe and other files. Try
a scandisk and a GCC reinstall (unzip gccnnnnb.zip again or re-download if
you nuked it or it's still broken after).
* GCC crash might be an isolated event, or one of the cases where the
stack should be edited larger; whereas the program crashing inconsistently
might be because it has a wild pointer, or uninitialized memory.
--
.*. Friendship, companionship, love, and having fun are the reasons for
-() < life. All else; sex, money, fame, etc.; are just to get/express these.
`*' Send any and all mail with attachments to the hotmail address please.
Paul Derbyshire ao950 AT freenet DOT carleton DOT ca pgd73 AT hotmail DOT com
- Raw text -