SuSE gcc blows up

[Gerry.Feldman at compaq.com (Jerry Feldman)]

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. 

On 10 Jul 2000, at 16:40, ccb at valinux.com wrote:

> 
> Fatal error 11 in gcc is usually an indication of a memory
> error.  Got Diagnostics?
> 
> 
> 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


--
Jerry Feldman
Contractor, eInfrastructure Partner Engineering   
508-467-4315 http://www.testdrive.compaq.com/linux/

Compaq Computer Corp.
200 Forest Street MRO1-3/F1
Marlboro, Ma. 01752
-
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).