Re: [Valgrind-developers] duplicate rw_remap in pthread_rwlock_unlock

[Darius I. <da...@ge...>]

On Sun, 27 Jun 2004, Tom Hughes wrote:

...
>
> > And another question:
> >
> > I looked at the vg_libpthread.c implementation for semaphores - they have
> > se_unmap(...) function for clear out place in the se_remap_* array. I dont
> > know if i'm right but it seems that it should work only for the last
> > (se_remap_used) member released. Otherwise you are getting hole in the
> > array - and the last member which is now in the position [se_remap_used+1]
> > gets inaccessible. It is nevermind if im right or wrong, i just want to
> > ask are you going to implement similar mechanism of reusing rw_remap_*
> > entries because when test program allocates rw_locks dynamically i'm
> > getting "VG_N_RWLOCKS is too low." very soon :(
>
> The se_unmap function no longer exists as the semaphore mapping scheme
> was changed a while ago to remove the limit on the number of semaphores.
>
> It sounds like a similar rework of rwlocks might be helpful to you?
Yes, you are right, I think that it will be helpful not only for me :)

--
DasI