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
Message-ID: <3BA53359.9040000@likai.net>
Date: Sun, 16 Sep 2001 19:18:49 -0400
From: Li-Kai Liu <news AT likai DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin <cygwin AT cygwin DOT com>, robert DOT collins AT itdomain DOT com DOT au
Subject: Re: icecast-1.3.11 port to cygwin
References: <3BA5218D DOT 6050005 AT likai DOT net> <009001c13f01$8fec9bd0$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

i'm just a poor fellow trying to port icecast to cygwin, and i'm not 
associated with icecast development team. :(

as i'm still studying the case myself, i just felt that I could make 
announcement based on what I already know. apparantly icecast uses their 
own thread management functions that traces active threads within the 
process. in cygwin prior to 1.3.3, icecast would complain during 
thread_init that "mt: thread never made to life ... weird" while the 
same time it says something like "unknown thread is running." I've 
reported to the icecast team and all they told me was not to use cygwin 
because pthread is broken. all I know is icecast tries to check the 
thread pointer using pthread_self() function and for some reason it 
doesn't return a reliable value.

i have a question though: does pthread_detach() in cygwin (before 1.3.3) 
change anything that is returned from pthread_self()? because i noticed 
how, after creating the thread, icecast calls this function. i strongly 
feel this has something to do with the phenomenon. anyhow, this problem 
is not present in cygwin 1.3.3 anymore, so i'd like to focus on other 
two problems.

- inability to catch signal ... i have no idea where to start finding 
the source of problem for this. can you give me a hint?
- coredump when waiting for threads to exit ... i will study this some more.

and as i said at the beginning, i'm not an active developer for icecast, 
so i'm just trying to bring icecast over to cygwin. the icecast 
developers don't seem to be keen about this port. (also, this is *not* 
my program).

liulk

Robert Collins wrote:

>Please do. I'm always interested in clear fault reports, or test cases.
>If you can generate a trivial testcase, or sometimes even just a good
>description of what is occuring in your program, I will endeavour to fix
>the bug.
>
>Rob
>



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