Date: Sun, 7 Nov 1999 17:20:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Gecko23 <gk_2345 AT my-deja DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Some error messages when using dialog...
In-Reply-To: <7vvbkl$4um$1@nnrp1.deja.com>
Message-ID: <Pine.SUN.3.91.991107171957.12805a-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 5 Nov 1999, Gecko23 wrote:

> > when I press CTRL-C it print this:
> [snipped traceback]
> 
> pressing CTRL-C generates SIGINT, which causes your
> program to abort. The abort triggers the traceback
> and dump.

This is not true: Ctrl-C does NOT cause a traceback.  It simply aborts
the program after printing a message like this:

    Exiting due to signal SIGINT
    INTR key pressed at eip=NNNNNNNN

Moreover, unlike other fatal signals, Ctrl-C even goes through the
normal exit procedure by calling `exit', rather than `_exit', as other
signals do.  So it even flushes the file buffers, closes any open
files, and calls all the functions registered with `atexit'.

> Personally I like being able to kill errant djgpp apps with ctrl-c,
> so I'm definately no expert on disabling it. I'm sure one of the more
> knowledgeable souls around here can help you with that.

It is all described in the docs.  Type "info libc alpha signal" and
read there.