SuSE gcc blows up

[James R. Van Zandt]

Charles C. Bennett, Jr.	 <ccb at valinux.com> writes:

>As I said in my last mail - the first symptom of bad memory is
>trouble from gcc.
>
>If you have a memory diagnostic tool, run it.

The explanation I've read is that gcc uses LOTS of pointers.  With bad
memory, most programs will tend to silently generate bad answers, but
gcc will tend to segfault.

	 - Jim Van Zandt

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).