Frank D. Engel, Jr. wrote:
Actually, by taking (of all things) *COMMENTS* out of my code, I can prevent it from compiling.
From compiling or crashing? If the former (and reproducibly), this would help.
Adriaan van Os wrote:
One way to do that is to use stress testing tools, which is why I were experimenting with the --param option (to stress test the gnu garbage collector). Also, I will see if I can build gpc with Apple's debugging version of malloc. But -- it could even be something as bizar as a bug in Mac OS X's disk cache system (I am just speculating). Frank mentioned hardware failures.
Not unlikely with the current temperatures, at least in Europe. Usually, my machine is quite reliable, but in the last few days it got a number of random crashes due to thermic problems. (Almost reproducible in that a longer optimizing compilation in the afternoon was quite likely to crash at some point ...) Frank -- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707