X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <loom.20090510T004554-316@post.gmane.org>
References: <9f8a01cd0905091706s6944a639m8da2f943212cc178 AT mail DOT gmail DOT com> 	 <loom DOT 20090510T004554-316 AT post DOT gmane DOT org>
Date: Sun, 10 May 2009 11:45:34 +0200
Message-ID: <9f8a01cd0905100245m16838bb9w3c6e494d4a03a4cb@mail.gmail.com>
Subject: Re: How to detect a cygwin thread?
From: Piotr Wyderski <piotr DOT wyderski AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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

Mark Geisert wrote:

> Why assume Cygwin could be the only source of extra threads?

There is no such assumption. But Cygwin is the only
source of threads that can stop the program entirely,
so they must be treated in an exceptional way.

> Wouldn't it make more sense to have your program remember its own threads and
> only suspend those?

No, the snapshot should be as exact as possible,
including "alien" threads. It has already proven to
be of key importance.

Best regards
Piotr Wyderski

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