Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!public!thad
From: thad@public.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.3b1
Subject: Re: gcc-cc1 dumping core and fatal signal 6
Keywords: gcc-cc1 core-dump
Message-ID: <3108@public.BTR.COM>
Date: 18 Jun 91 13:38:24 GMT
References: <125@morwyn.UUCP> <1991Jun17.222609.10606@blilly.UUCP>
Organization: BTR Public Access UNIX, Mountain View CA
Lines: 20

In article <1991Jun17.222609.10606@blilly.UUCP> bruce@balilly (Bruce Lilly) writes:
>In article <125@morwyn.UUCP> forrie@morwyn.UUCP (Forrie Aldrich) writes:
>[ ... ]
>>Program cc1 got fatal signal 6.
>[ ... ]
>>I can't place any calls to gcc-cc1, as it will simply dump core.
>>[...]

I used to get ``fatal signal 6'' and ``fatal signal 11'' OFTEN before upgrading
to 3.51m.  Arrgh, the frustrations of compiling large programs ... sometimes
required 15 to 20 "nohup make &" before it'd complete successfully (even with
kernel version 3.51a).

One of the release notes (either net-posted or accompanying FIXDISK 2)
mentioned a long-standing kernel bug in this regards was fixed by 3.51m.

The only gripe I have concerns 19,200 baud operation ("Oh gawd, Thad, let it
rest!" :-)

Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]