Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Sun, 16 Sep 2001 19:52:53 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: icecast-1.3.11 port to cygwin
Message-ID:	<20010916195253.A6470@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3BA5218D DOT 6050005 AT likai DOT net> <009001c13f01$8fec9bd0$0200a8c0 AT lifelesswks> <3BA53359 DOT 9040000 AT likai DOT net> <00c101c13f09$6dac0490$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
In-Reply-To:	<00c101c13f09$6dac0490$0200a8c0@lifelesswks>
User-Agent:	Mutt/1.3.21i

On Mon, Sep 17, 2001 at 09:43:45AM +1000, Robert Collins wrote:
>> - inability to catch signal ... i have no idea where to start finding
>> the source of problem for this. can you give me a hint?
>
>Well to start with grab the Cygwin source
>(http://www.cygwin.com/contrib.html) and build yourself a debug .dll.
>(You'll need that :} ).
>
>Chris Faylor just wrote a "how-signals-works.txt" file, which you will
>find in the source tarballs. Read that. Then start test cases I guess.

One thing that I should mention is that signals only work with cygwin
functions.  You can't do a "ReadFile" or a "Sleep" and expect the call
to be interrupted by a signal.

So, if icecast is mixing Windows functions and UNIX signals this will
be a problem.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -