SuSE gcc blows up

[ccb at valinux.com]

> It's nearly always a seg fault. As I mentioned, I have not have GCC 
> segfault on me in the recent SuSE releases. I would like to get a pointer 
> to the source code that caused GCC to segfault. Even with bad source 
> code, compilers should not segfault. 

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.


ccb

--
Charles C. Bennett, Jr.			VA Linux Systems
Systems Engineer,			25 Burlington Mall Rd., Suite 300
US Northeast Region			Burlington, MA 01803-4145
+1 617 543-6513				+1 888-LINUX-4U
ccb at valinux.com				www.valinux.com
 vi/(emacs)  NT/(Linux)  qmail/(sendmail)  (perl)/python  (pepsi)/coke
-
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).