X-Spam-Check-By:	sourceware.org
Message-ID:	<447886F9.7000806@kleckner.net>
Date:	Sat, 27 May 2006 10:06:01 -0700
From:	Jim Kleckner <jek-cygwin1 AT kleckner DOT net>
User-Agent:	Thunderbird 1.5 (Windows/20051230)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin G++ bug? - Python Extension module #including <iostream> dies before initialization
References:	<44775331 DOT 4070809 AT ukf DOT net> <44786EAA DOT 9020002 AT kleckner DOT net> <44787848 DOT 1BD5F4CF AT dessent DOT net>
In-Reply-To:	<44787848.1BD5F4CF@dessent.net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Brian Dessent wrote:
> As you can see, this all is contingent upon a program like GDB using the
> Windows debug API.  Without that, the entire issue is irrelevant, so I
> can't see how this possibly would apply to Python.
>   

Thanks for explaining how the Windows debug API is the one
actually catching the exception rather than GDB directly
changing how exceptions are caught.  This is useful.

I will be surprised if there doesn't turn out to be some
commonality between the pthread_mutex_init issue
and something Python is doing either directly or
via the use of dlopen().

Thanks - Jim

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

- Raw text -