Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID:	<20041122180325.75663.qmail@web60809.mail.yahoo.com>
Date:	Mon, 22 Nov 2004 10:03:25 -0800 (PST)
From:	Peter Xiaochuan Huang <xchuang AT yahoo DOT com>
Subject:	Oct. pthread problem seems still there
To:	cygwin AT cygwin DOT com
MIME-Version:	1.0

I am using pthread extensively in my program and I am
getting problem from pthread similar to those posted
in October in this same mailing list.

The problems can described as below:
1. It seems that main execution thread randomly hangs
while the dispatched threads are joined or collected.
It happens more often when memory gets tighter.

2. When I tried to trace it using gdb, it always
crashes and leave a stack without much information. In
the stack it only has kernel32,
setThreadExecutionState, and get_retrant() system
calls in it.

Sorry that I can not offer a simplified test case. I
hope it will help people who already handled the
problem to look into it again.

It is the same whether I use 1.15.2 release or the
snap shot of Nov 17 of cygwin. Though it seems
happening less often in Nov 17 snap hot.

Thanks if anyone can offer insight into this.

-Peter




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

- Raw text -