SuSE gcc blows up

[Derek Martin]

On Tue, 11 Jul 2000 ccb at valinux.com wrote:

> 
> > 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.

I agree that's the most likely cause, but there are others.  I meant to
post on this topic earlier but couldn't find the document I was looking
for until now.

If your /usr/doc structure looks like RedHat's, have a look at the file

  /usr/doc/FAQ/txt/GCC-SIG11-FAQ

If you don't have the file, I'll mail it to you.


-- 
Derek Martin
System Administrator
Mission Critical Linux
martin at MissionCriticalLinux.com 

-
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).