Identifying pthread threading bug

Identifying pthread threading bug

[Roger Leigh]

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.


Many thanks,
Roger

-- 
Roger Leigh

                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.

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

Re: Identifying pthread threading bug

[Yaakov Selkowitz]

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