From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Win8 issue with pthread_once in ctor? (Re: Is there someone who have a same problem ?)
Date: Thu, 23 Jan 2014 10:32:00 -0000 [thread overview]
Message-ID: <20140123103209.GM2357@calimero.vinschen.de> (raw)
In-Reply-To: <52E0A694.8090304@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
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@entry=0x239c68,
> magic=magic@entry=3742232649, static_ptr1=static_ptr1@entry=0x0,
> static_ptr2=static_ptr2@entry=0x0,
> static_ptr3=static_ptr3@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.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-01-23 10:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 4:18 Is there someone who have a same problem ? kou1okada
2014-01-22 5:43 ` Yaakov (Cygwin/X)
2014-01-22 8:35 ` kou1okada
2014-01-22 12:17 ` Tim Prince
2014-01-22 16:29 ` kou1okada
2014-01-22 16:36 ` Adam Dinwoodie
2014-01-22 17:15 ` Balaji Venkataraman
2014-01-22 20:33 ` Csaba Raduly
2014-01-22 21:43 ` Thomas Wolff
2014-01-23 3:19 ` kou1okada
2014-01-23 3:07 ` kou1okada
2014-01-22 21:56 ` Yaakov (Cygwin/X)
2014-01-23 5:20 ` Win8 issue with pthread_once in ctor? (Re: Is there someone who have a same problem ?) Yaakov (Cygwin/X)
2014-01-23 10:32 ` Corinna Vinschen [this message]
2014-01-23 13:09 ` Christopher Faylor
2014-01-24 7:57 ` Is there someone who have a same problem ? Yaakov (Cygwin/X)
2014-01-24 12:53 ` kou1okada
2014-01-23 9:08 ` Yaakov (Cygwin/X)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140123103209.GM2357@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).