This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Question on when __pthread_lock second parameter shoudl be NULL
- To: Ulrich Drepper <drepper at cygnus dot com>
- Subject: Re: Question on when __pthread_lock second parameter shoudl be NULL
- From: Kaz Kylheku <kaz at ashi dot footprints dot net>
- Date: Wed, 9 Aug 2000 21:40:54 -0700 (PDT)
- cc: libc-alpha at sources dot redhat dot com
On 9 Aug 2000, Ulrich Drepper wrote:
> > This issue still exists on the main trunk! Ulrich, can you commit a fix?
>
> No no, look at the code. If we actually get the self pointer we pass
> it down. In the case of PTHREAD_MUTEX_ADAPTIVE_NP we don't need self
> in the mutex function and therefore pass NULL.
Right; I realized that I somehow confused myself between branches on cvsweb,
but didn't feel that it was worthwhile to follow up---until now. ;)