Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!unhd.unh.edu!unhtel!morwyn!forrie
From: forrie@morwyn.UUCP (Forrie Aldrich)
Newsgroups: comp.sys.3b1
Subject: gcc-cc1 dumping core and fatal signal 6
Keywords: gcc-cc1 core-dump
Message-ID: <125@morwyn.UUCP>
Date: 15 Jun 91 18:18:27 GMT
Article-I.D.: morwyn.125
Organization: CREATIVE CONNECTIONS - Dover, NH - USA
Lines: 26

Once again, I ask if anyone out there is having this same problem with
the latest release of gcc (1.40)... whenever I go to compile something
no matter what it is I get the message:

gcc version 1.40
 /usr/local/lib/gcc-cpp -v -undef -D__GNUC__ -Dmc68k -Dunix -Dunixpc -D__mc68k__ -D__unix__ -D__unixpc__ -D__OPTIMIZE__ binmail.c /usr/tmp/cca11801.cpp
GNU CPP version 1.39
 /usr/local/lib/gcc-cc1 /usr/tmp/cca11801.cpp -quiet -dumpbase binmail.c -O -version -o /usr/tmp/cca11801.s
Program cc1 got fatal signal 6.

And when I check the version of gcc-cc1 I get this:

1.40

I can't place any calls to gcc-cc1, as it will simply dump core.  Could this be
due to a bad transfer?  Is ANYONE ELSE OUT THERE HAVING THIS PROBLEM???


-- 

--------------------=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--------------------
Forrest Aldrich, Jr.|   (a reliable path here someday)   |forrie@morwyn.UUCP
                    |           <email paths>            | 
CREATIVE CONNECTIONS|  uunet!virgin!unhtel!morwyn!forrie |Graphic Illustration
------------------\-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=/------------------
                   \___ PO Box 1541 - Dover, NH  03820 ___/