Date: Tue, 15 Nov 2005 18:00:31 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Joe Smith <unknown_kev_cat AT hotmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Can I get a sigint when the bash window closed with close window's  button?
In-Reply-To: <dldodk$eod$1@sea.gmane.org>
Message-ID: <Pine.GSO.4.63.0511151757160.3862@slinky.cs.nyu.edu>
References: <896835389 AT web DOT de> <Pine DOT GSO DOT 4 DOT 63 DOT 0511151424250 DOT 15491 AT slinky DOT cs DOT nyu DOT edu>  <dldodk$eod$1 AT sea DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Tue, 15 Nov 2005, Joe Smith wrote:

> "Igor Pechtchanski" <pechtcha AT XX DOT XXX DOT XXX> wrote in message news:Pine DOT GSO DOT 4 DOT 63 DOT 0511151424250 DOT 15491 AT slinky DOT cs DOT nyu DOT edu...

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> > On Tue, 15 Nov 2005, Konrad Eisele wrote:
> >
> > > When th cygwin bash window is closed by clicking on the window's
> > > close button the the appliaction gets killed without recieving a
> > > sigint or any atexit called. Is there a way to be able to run
> > > cleanup code when the application is about to be killed?
> >
> > According to exceptions.cc, a SIGHUP will be sent to bash in this
> > case. Are you handling the right signal?
> >
> > BTW, the atexit() callback also should be called -- do you have a
> > simple testcase to reproduce the problem?
> > Igor
>
> I know nothing about signals, but this program when run inside bash does
> not seem to run callback() *ever*.
> ^c does not run it. Closing the bash window does not run it. But if you
> remove the loop then it *is* run.
>
> #include <stdio.h>
> void callback()
> {
>  FILE *current;
>
>  current=fopen("test.txt","a");
>  fprintf(current,"atexit");
> }
>
> int main()
> {
>  atexit(*callback);
>  while(1)
>  {};
> }

IIRC, the atexit callback is not supposed to be invoked from a default
signal handler.  In fact, Cygwin defines a signal_exit specifically to
avoid invoking it.  If you change the above to terminate on something
other than a signal (e.g., a condition in the loop), your callback will be
invoked.  Adding a signal handler that calls exit() should also cause the
callback to be invoked.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/