From: 陈晓晖 <xhchen8018@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [pthread] pthread+printf may have bugs
Date: Thu, 25 Dec 2008 02:53:00 -0000 [thread overview]
Message-ID: <6aa8c88e0812241852i7aa64645xe27cd5e343ca2055@mail.gmail.com> (raw)
In-Reply-To: <6aa8c88e0812240054m6a13857uee028380f5d04862@mail.gmail.com>
It is strange that the error disappeared if replacing any cygwin1.dll
on the snapshot page
http://cygwin.com/snapshots/
For these versions, I see a more line "Huh? No /etc/fstab file?
Using default root and cygdrive prefix..." was printed.
By the way, does anybody know where can I find the pthread source for
cygwin? is it pthread-win32? Thanks ..
I want to look into it.
2008/12/24 陈晓晖 <xhchen8018@gmail.com>:
> Hi,
>
> I found that pthread may stop work if using printf in thread.
> I'm not sure that printf is thread safe or not, so I tried to wrap the
> printf with a mutex, but the problem still exists.
> After I removed all printfs, everything is OK.
>
next prev parent reply other threads:[~2008-12-25 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 8:55 陈晓晖
2008-12-25 2:53 ` 陈晓晖 [this message]
2008-12-25 4:16 ` Christopher Faylor
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=6aa8c88e0812241852i7aa64645xe27cd5e343ca2055@mail.gmail.com \
--to=xhchen8018@gmail.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).