Pthreads-w32 on Win2k+Cygwin env.

Pthreads-w32 on Win2k+Cygwin env.

[Ildar Mulyukov]

Hi guys!

The thing is I've tried this pthreads-snap-2000-12-29 on my environment.
I have Win2k localized(russian) + Cygwin crosscompiler (to MinGW).

This pthreads doesn't work for me :-(

Libs are built after I've added -mno-cygwin in makefiles (GNUmakefile).
But test mutex1 fails on pthread_mutex_destroy. Gdb backtrace:

#0  0x00403194 in pthread_getspecific (key=0x0) at tsd.c:325
#1  0x00401d8d in pthread_self () at misc.c:161
#2  0x00401cc3 in pthread_mutex_trylock (mutex=0x247ff38) at mutex.c:686
#3  0x004017f8 in pthread_mutex_destroy (mutex=0x4080b4) at mutex.c:216
#4  0x00401535 in main () at mutex1.c:27

Could anyone explain me this behaviour?
Thank you in advance, Ildar.

Re: Pthreads-w32 on Win2k+Cygwin env.

[Ildar Mulyukov]

I am very sorry for I disturbed you all in vain. That was my fault - I
forgot to set -mno-cygwin for linking.

I suppose GNUmakefile's should support of Cygwin with MinGW crosscompiling
using Danny's runtime at
http://au.y42.briefcase.yahoo.com/danny_r_smith_2001

Unfortunately I still have problems with my configuration, but it's the
topic of my next letter.

Thank you all, Ildar.


----- Original Message -----
From: "Ildar Mulyukov" <ildar@sendmail.ru>
To: "Ildar Mulyukov" <ildar@sendmail.ru>
Sent: Tuesday, June 05, 2001 11:26 AM
Subject: Re: Pthreads-w32 on Win2k+Cygwin env.


> I am very sorry for I disturbed you all in vain. That was my fault - I
> forgot to set -mno-cygwin for linking.
>
> I suppose GNUmakefile's should support of Cygwin with MinGW crosscompiling
> using Danny's runtime at
> http://au.y42.briefcase.yahoo.com/danny_r_smith_2001
>
> Unfortunately I still have problems with my configuration, but it's the
> topic of my next letter.
>
> Thank you all, Ildar.
>
> ----- Original Message -----
> From: "Ildar Mulyukov" <ildar@sendmail.ru>
> To: <pthreads-win32@sources.redhat.com>
> Sent: Monday, June 04, 2001 11:28 AM
> Subject: Pthreads-w32 on Win2k+Cygwin env.
>
>
> > Hi guys!
> >
> > The thing is I've tried this pthreads-snap-2000-12-29 on my environment.
> > I have Win2k localized(russian) + Cygwin crosscompiler (to MinGW).
> >
> > This pthreads doesn't work for me :-(
> >
> > Libs are built after I've added -mno-cygwin in makefiles (GNUmakefile).
> > But test mutex1 fails on pthread_mutex_destroy. Gdb backtrace:
> >
> > #0  0x00403194 in pthread_getspecific (key=0x0) at tsd.c:325
> > #1  0x00401d8d in pthread_self () at misc.c:161
> > #2  0x00401cc3 in pthread_mutex_trylock (mutex=0x247ff38) at mutex.c:686
> > #3  0x004017f8 in pthread_mutex_destroy (mutex=0x4080b4) at mutex.c:216
> > #4  0x00401535 in main () at mutex1.c:27
> >
> > Could anyone explain me this behaviour?
> > Thank you in advance, Ildar.
> >
> >
>

RE: Pthreads-w32 on Win2k+Cygwin env.

[Bossom, John]

I am surprised to see a call to pthread_mutex_trylock from within
pthread_mutex_destroy.
I am also surprised to see a call to pthread_self from
pthread_mutex_trylock.

In the end, you will notice that the key passed into pthread_getspecific is
0 (zero) indicating
that it either hasn't been initialized yet or has already been destroyed.

You did not indicate if you are using the static library or the DLL. I am
betting you are
linking against the static library which, I believe, requires an
initialization and terminate call.
The DLL version is self boot-strapping...

-----Original Message-----
From: Ildar Mulyukov [ mailto:ildar@sendmail.ru ]
Sent: June 4, 2001 3:28 AM
To: pthreads-win32@sources.redhat.com
Subject: Pthreads-w32 on Win2k+Cygwin env.


Hi guys!

The thing is I've tried this pthreads-snap-2000-12-29 on my environment.
I have Win2k localized(russian) + Cygwin crosscompiler (to MinGW).

This pthreads doesn't work for me :-(

Libs are built after I've added -mno-cygwin in makefiles (GNUmakefile).
But test mutex1 fails on pthread_mutex_destroy. Gdb backtrace:

#0  0x00403194 in pthread_getspecific (key=0x0) at tsd.c:325
#1  0x00401d8d in pthread_self () at misc.c:161
#2  0x00401cc3 in pthread_mutex_trylock (mutex=0x247ff38) at mutex.c:686
#3  0x004017f8 in pthread_mutex_destroy (mutex=0x4080b4) at mutex.c:216
#4  0x00401535 in main () at mutex1.c:27

Could anyone explain me this behaviour?
Thank you in advance, Ildar.