Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <40B4BA71.2040501@ics.de>
Date: Wed, 26 May 2004 17:40:33 +0200
From: Thomas Kloeber <kloeber@ics.de>
Reply-To: kloeber@ics.de
Organization: ICS GmbH (http://www.ics.de)
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Signal Handling of cygwin under VMware Workstation
References: <40B4A7CB.1000402@ics.de> <20040526143910.GB981@coe.bosbc.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Chris,

Christopher Faylor wrote:

>None.  I use VMware all of the time in cygwin development.
>  
>
looks like you're right. further tests show that it is a question, which 
shell i use:

    * ksh and bash: the test program receives the signal and terminates
    * sh: the test program receives the signal and then performs its
      signal handling procedure

(under Solaris 2.8 the test program on all shells shows the correct 
behaviour.)

if i use kill() to send a SIGINT to my test program running on

    * ksh and bash: it terminates without receiving the signal
    * sh: it doesn't receive the signal at all

any ideas/guesses are appreciated.

thomas

-- 
It has never been easier to help someone who suffers from hunger,
and use the web for a good purpose: http://www.thehungersite.com/


--
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/