X-Recipient: archive-cygwin@delorie.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: <20090510202132.GB25909@ednor.casa.cgf.cx> References: <9f8a01cd0905091706s6944a639m8da2f943212cc178@mail.gmail.com> <9f8a01cd0905100245m16838bb9w3c6e494d4a03a4cb@mail.gmail.com> <20090510202132.GB25909@ednor.casa.cgf.cx> Date: Mon, 11 May 2009 00:33:07 +0200 Message-ID: <9f8a01cd0905101533i2902636aub172298be61599a5@mail.gmail.com> Subject: Re: How to detect a cygwin thread? From: Piotr Wyderski To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Christopher Faylor wrote: > The closest API to it would be a call to > cygwin_internal(CW_GETTHREADNAME, ); Now it works like a charm. The internal thread which suspension leads to program hangup is named "sig". > =A0This is an as-is undocumented interface and we make no guarantees that= its > behavior will remain consistent across releases. Of course. Thanks! > > cgf > > -- > Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple > Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html > Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html > FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/ > > -- 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/