public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Is there someone who have a same problem ?
Date: Fri, 24 Jan 2014 07:57:00 -0000	[thread overview]
Message-ID: <52E21CF9.8070003@users.sourceforge.net> (raw)
In-Reply-To: <20140123103209.GM2357@calimero.vinschen.de>

On 2014-01-23 04:32, Corinna Vinschen wrote:
> On Jan 22 23:20, Yaakov (Cygwin/X) wrote:
>> 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.

And, of course, without optimization it works.  So, I managed to narrow 
this down to the ctor itself: compiling it with -O0 or -O1 works, but 
not with -O2 or -O3; other functions seem to be fine at -O2.  The 
diffstat between the resulting assemblies of that file is huge, so I 
haven't diagnosed the actual cause yet.  Feel free to let me know if 
you're interested. :-)

In the meantime, the workaround is easy, so I just uploaded 
p11-kit-0.18.7-2 and ca-certificates-1.96-2 for x64 only.  If you are 
running 64-bit Cygwin on Windows 8.0 x64, those releases should fix this 
for you.


Yaakov


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

  parent reply	other threads:[~2014-01-24  7:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  4:18 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
2014-01-23 13:09           ` Christopher Faylor
2014-01-24  7:57           ` Yaakov (Cygwin/X) [this message]
2014-01-24 12:53             ` Is there someone who have a same problem ? 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=52E21CF9.8070003@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --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).