> Yes, if compiling had been working fine before, this is likely memory
> going bad.
I've also seen errors such as this when you run out of swap. A malloc
request fails and if the code doesn't check the return, you get the
sigsegv dereferencing a bad pointer.
FWIW,
Pat
--
Patrick O'Rourke
[EMAIL PROTECTED]
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
