X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Sun, 10 May 2009 23:18:01 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: How to detect a cygwin thread?
Message-ID: <20090511031800.GG25909@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
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> <9f8a01cd0905101752ue79f6f8v69b4163b02a1ff57@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9f8a01cd0905101752ue79f6f8v69b4163b02a1ff57@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Mon, May 11, 2009 at 02:52:27AM +0200, Piotr Wyderski wrote:
>Christopher Faylor wrote:
>
>>?This isn't a bug in Cygwin.
>
>I've never made a statement that it is.

And I never claimed that you made a statement that it is so I guess
everything is hunky dory.

>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.  ?Not 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.

Ok, then.  From everything you've described, you are relying on fragile
behavior that has nothing to do with Cygwin but if you're ok with the
possibility that your program could hang occasionally then there's just
more hunky doryness.

cgf

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

