Date: Sun, 13 Mar 94 15:15:34 EST
From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
To: dridge AT MIT DOT EDU
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Ctrl-Break, Ctrl-C
Reply-To: babcock AT cfa DOT harvard DOT edu

> Often when I'm compiling I'll want to kill the compile halfway through,
> as it isn't too fast on my machine.
> Hitting 'Ctrl-Break' only seems to make the machine pause, print out
> stack & register information, and then it carries on its merry way...

This might be a quirk of your make program.  I'm able to abort a series of
compilations by hitting control-c using OPUS MAKE.  Another possibility is
how are you invoking gcc?  I compile one routine at a time, effectively doing
   gcc foo1.c
   gcc foo2.c
   ...
The behavior might be different for
   gcc foo1.c foo2.c ...

Beware of hitting control-break.  Go32 leaves the control-break interrupt
pointing into itself when it terminates which is not a good thing.  There was
some discussion of how to fix this a few weeks ago, so I think it will be
fixed in the next maintenance release.