MIME-Version: 1.0
In-Reply-To: <20090511002739.GF25909@ednor.casa.cgf.cx>
References: <9f8a01cd0905091706s6944a639m8da2f943212cc178@mail.gmail.com> 	 <loom.20090510T004554-316@post.gmane.org> 	 <9f8a01cd0905100245m16838bb9w3c6e494d4a03a4cb@mail.gmail.com> 	 <loom.20090510T184100-821@post.gmane.org> 	 <20090510202132.GB25909@ednor.casa.cgf.cx> 	 <9f8a01cd0905101533i2902636aub172298be61599a5@mail.gmail.com> 	 <20090510233629.GC25909@ednor.casa.cgf.cx> 	 <9f8a01cd0905101707x2b91f1edg33ae17ec82ab722e@mail.gmail.com> 	 <20090511002739.GF25909@ednor.casa.cgf.cx>
Date: Mon, 11 May 2009 02:52:27 +0200
Message-ID: <9f8a01cd0905101752ue79f6f8v69b4163b02a1ff57@mail.gmail.com>
Subject: Re: How to detect a cygwin thread?
From: Piotr Wyderski <piotr.wyderski@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Christopher Faylor wrote:

>=A0This isn't a bug in Cygwin.

I've never made a statement that it is. It's just
an unexpected and undesired behaviour I wanted
to get rid of. The context was there to make it
clear what exactly is happening on that particular
control flow path.

> Your takeaway from this is:
>
> 1) I don't care about this. =A0Not suspending the "sig" thread fixes my
> problem.

Yes, it does. And since when it happens, the
program is about to die anyway, I don't think
that tracking its exact causes is worth of my
effort.

> =A0We try hard not to call SuspendThread when the program is in the middl=
e of
> a Windows call.

I don't use the function either, except when
under abnormal circumstances, when I have
the very last chance to report a problem.

Piotr

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