X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.5 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: <4A075D56.30708@gmail.com> References: <9f8a01cd0905091706s6944a639m8da2f943212cc178@mail.gmail.com> <9f8a01cd0905100245m16838bb9w3c6e494d4a03a4cb@mail.gmail.com> <20090510202132.GB25909@ednor.casa.cgf.cx> <9f8a01cd0905101533i2902636aub172298be61599a5@mail.gmail.com> <4A075D56.30708@gmail.com> Date: Mon, 11 May 2009 02:20:11 +0200 Message-ID: <9f8a01cd0905101720w7d6a3f06jae04197433240b70@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 Dave Korn wrote: > =A0Is there a POSIX way of doing what you want? I don't think so. This particular module contains so much concentration of low-level magic (GetThreadSelectorEntry + manual N= T_TIB access in Garry Nebbett's style, to name some techniques) to extract as accurate machine state description as possible. Mostly OS-specific guts far beyond POSIX specs and definitely nothing portable. 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/