diff options
author | rpj <rpj> | 2005-05-08 16:55:02 +0000 |
---|---|---|
committer | rpj <rpj> | 2005-05-08 16:55:02 +0000 |
commit | ac8e3d247fa03af61b5411f92508481e7c3f49f8 (patch) | |
tree | f5d9c2a8bc58a2e6135e8aa2b207daab23de14a7 /NEWS | |
parent | 7523c7c4d75652f67cd31cb123e1268790394c8b (diff) |
''
Diffstat (limited to 'NEWS')
-rw-r--r-- | NEWS | 17 |
1 files changed, 13 insertions, 4 deletions
@@ -1,6 +1,6 @@ RELEASE 1.9.0 ------------- -(2005-05-06) +(2005-05-09) General ------- @@ -16,9 +16,13 @@ http://sources.redhat.com/pthreads-win32/manual/index.html Bugs fixed ---------- -* Thread Specific Data (TSD) key management has been altered to -eliminate a source of resource leakage (HANDLEs plus memory). -Thanks to Richard Hughes at Aculab for identifying the leak. +* Thread Specific Data (TSD) key management has been ammended to +eliminate a source of (what was effectively) resource leakage (HANDLEs +plus memory). +Thanks to Richard Hughes at Aculab for identifying and locating the leak. + +* TSD key destructors are now processed up to PTHREAD_DESTRUCTOR_ITERATIONS +times (was always in pthread.h) instead of just once. * Fix a semaphore accounting race between sem_post/sem_post_multiple and sem_wait cancellation. This is the same issue as with @@ -40,6 +44,11 @@ from the last release. It's not a part of the regular test suite because it can take awhile to run. To run it: nmake clean VC-stress +* tsd2.c - tests that key destructors are re-run if the tsd key value is +not NULL after the destructor routine has run. Also tests that +pthread_setspecific() and pthread_getspecific() are callable from +destructors. + RELEASE 1.8.0 ------------- |