DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=cleOof6UyBfND/kzlb2fKCihgZJMyn6Z+fcjIMIriOk8w1LbDTiWA
	yEmtOHH7cjLFfq81dO9uUngWgsaRZPTZ7Bcf+lJzzFAEvlhHGXg50x8pYfHtrO+J
	5Z+XYTcXXaJKv73/qfWaT9wezKG0sN+R/2NOnNlCaIYfgJ9rsf9qSk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Thu, 23 Jan 2014 08:09:41 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Win8 issue with pthread_once in ctor? (Re: Is there someone who have a same problem ?)
Message-ID: <20140123130941.GC7177@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CA+WgaY86qXwc9ywzjmU1x8B9WrpFnsQzFtvs6q5JLTRDFsEvHQ AT mail DOT gmail DOT com> <52DF5A6F DOT 2030509 AT users DOT sourceforge DOT net> <CA+WgaY-7sVhxcKyaY=FZpSbiG3JW8N+KHRAh=oXyh_A3bWeH5A AT mail DOT gmail DOT com> <52E03E99 DOT 9050205 AT users DOT sourceforge DOT net> <52E0A694 DOT 8090304 AT users DOT sourceforge DOT net> <20140123103209 DOT GM2357 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140123103209.GM2357@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Jan 23, 2014 at 11:32:09AM +0100, Corinna Vinschen wrote:
>On Jan 22 23:20, Yaakov (Cygwin/X) wrote:
>> On 2014-01-22 15:56, Yaakov (Cygwin/X) wrote:
>> >>I believe that there is a problem when p11-kit command runs on the
>> >>cygwin64 under Windows 8.
>> >
>> >Confirmed with a fresh Windows 8 x64 installation, but not with 8.1.
>> >I'll have to look into this further.
>> 
>> Here's what I've found so far:
>> 
>> So far only with Cygwin64 on Windows 8.0 x64 (but not with Cygwin32
>> even on 8.0 x64, nor with Cygwin64 on Windows 7 or 8.1), running any
>> of the p11-kit commands in ca-certificates' postinstall under strace
>> shows an exception c0000005 at 0x180134b75 immediately after loading
>> /usr/lib/pkcs11/p11-kit-trust.so, which translates to:
>> 
>> $ addr2line -fp -e /usr/bin/cygwin1.dll 0x180134b75
>> verifyable_object_isvalid at
>> /usr/src/debug/cygwin-1.7.27-2/winsup/cygwin/thread.cc:144
>> 
>> And eventually on a call to that function:
>> 
>> verifyable_object_isvalid (objectptr=objectptr AT entry=0x239c68,
>> magic=magic AT entry=3742232649, static_ptr1=static_ptr1 AT entry=0x0,
>> static_ptr2=static_ptr2 AT entry=0x0,
>> static_ptr3=static_ptr3 AT entry=0x0)
>> at /usr/src/debug/cygwin-1.7.27-2/winsup/cygwin/thread.cc:140
>> 140   if((static_ptr1 && *object == static_ptr1) ||
>> 144   if((*object)->magic != magic)
>> [Inferior 1 exited with code 030000000005]
>> 
>> Now the strange thing about this module is that it has a constructor
>> which calls pthread_once() on a function which creates a recursive
>> mutex, so just dlopen()ing is enough.  Unfortunately, my attempts to
>> reproduce this with an STC have not been successful.
>> 
>> Corinna, cgf, any insights?
>
>Except for the content of object apparently being off, no.  It would
>be helpful to build p11-kit with debugging and without optimization
>and then step right into it, otherwise it's pretty hard to say
>anything useful.

What she said.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple