Dec. 23, 2006
7:30 p.m.
On Saturday 23 December 2006 19:08, Eric Martin wrote:
Is there anything I can do aside from piping the output to a file to capture what the problem might be (tried it, not much help)?
it depends on the error if gcc is randomly ICEing, then it can commonly be caused by: - not enough physical ram - flaky hardware - flaky ram - cpu overheating the exact error message would point in the direction -mike