From: Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: Identifying pthread threading bug
Date: Mon, 24 May 2004 16:34:00 -0000 [thread overview]
Message-ID: <40B21E36.4070600@users.sourceforge.net> (raw)
In-Reply-To: <20040524132428.GA1462@system10>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roger Leigh wrote:
| I am building glib on cygwin, using this release:
|
|
http://ftp.gnome.org/pub/GNOME/desktop/2.6/2.6.1/sources/glib-2.4.1.tar.bz2
|
| When I build with
|
| ./configure -C --prefix=/usr --enable-threads --with-libiconv \
| --enable-shared --disable-static
|
| the build succeeds, but the unit test test/child-test waits indefinitely
| on a child.
|
| When I build with
|
| ./configure -C --prefix=/usr --disable-threads --with-libiconv \
| --enable-shared --disable-static
|
| the test succeeds.
|
| I infer that the problem is due to enabling threading, and since the
| code works on most, if not all, other platforms supporting POSIX
| threads, I think it's likely that it's doing something that Cygwin
| doesn't like, or is racy. Could anyone suggest how I might track down
| the cause of the problem? I'm not particularly familiar with the Cygwin
| internals, or threading, but I'm OK with gdb and C.
I suggest you visit the CyGnome2 project at
http://cygnome2.sourceforge.net/ and perhaps ask this question on their
cygnome2-devel list. I know the project head has built GTK+ 2.4 but
hasn't released it due to bugs; I think he could give you more details.
Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAsh40piWmPGlmQSMRAvhJAJ9eMfnFrmKZ9Lu7cydmCXr37+dodgCfdrw5
kNzfK0zXlxpRhLXrcyxcZ5o=
=yN8p
-----END PGP SIGNATURE-----
--
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/
prev parent reply other threads:[~2004-05-24 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 15:48 Roger Leigh
2004-05-24 16:34 ` Yaakov Selkowitz [this message]
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=40B21E36.4070600@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).