Article-I.D.: decwrl.6537
Posted: Fri Nov 21 14:06:21 1986
Date-Received: Fri, 21-Nov-86 21:58:55 EST
Sender: daemon@decwrl.DEC.COM
Organization: Digital Equipment Corporation
Lines: 22

Why does cc sometimes quit as soon as it's been loaded into memory?  One reason
I've found is the following:

I like to do my editing with MicroEmacs (version 3.7, incase this "feature" 
isn't shared with the other dialects of microemacs).  Whenever I use a
Control-C, Control-D, Control-E or Control-F command, the appropriate signal
bit gets set for the task (the CLI that ran us).  Exitting the editor doesn't
do anything to clear these signal bits.  Next time I run a program that cares
about them (and cc or make are prime examples), it'll think it just got the
corresponding signal.

The appropriate thing to do (although I haven't done it yet myself) is to put
some code in MicroEmacs under the Amiga conditional to clear the signal bits
before exitting, so we don't screw anyone else up farther down the line.

Either way, as the code stands now, it's a solidly reproducible case.

{insert your favorite disclaimer here}

(DEC E-NET)	Viking::Banks
(UUCP)		{decvax, ucbvax, allegra}!decwrl!dec-rhea!dec-Viking!Banks
(ARPA)		Banks%Viking.DEC@decwrl.ARPA