summaryrefslogtreecommitdiffstats
path: root/test/ttsafe_cancel.c
diff options
context:
space:
mode:
authorBill Wendling <wendling@ncsa.uiuc.edu>2000-05-19 22:02:24 (GMT)
committerBill Wendling <wendling@ncsa.uiuc.edu>2000-05-19 22:02:24 (GMT)
commitb97c63cdbcdcf3f575aedfbfb3b2e00e2a28be60 (patch)
treed817141cf75aad516b6f8571eff324eddb7247ad /test/ttsafe_cancel.c
parentfb75b8a89ce45af2ac6c14ed31ffc884b0d0fc88 (diff)
downloadhdf5-b97c63cdbcdcf3f575aedfbfb3b2e00e2a28be60.zip
hdf5-b97c63cdbcdcf3f575aedfbfb3b2e00e2a28be60.tar.gz
hdf5-b97c63cdbcdcf3f575aedfbfb3b2e00e2a28be60.tar.bz2
[svn-r2286] Gave the threading functions return types (herr_t). pthreads' calls
return 0 on success and non-zero on failure. That's what happens with these calls. There was a problem compiling threading on Linux. The pthread_t type is not consistent among different implementations, so it cannot simply be assigned to NULL or tested against it. I initialize it by calling HDmemset(foo_thread, 0, sizeof(pthread_t)). To see if it's a "null" pthread, I created a special pthread_t object (assigned to only in the init phase and then only read...i.e., thread safe) and assigned it "null" as above. Then I use pthread_equal() to determine if the thread is null.
Diffstat (limited to 'test/ttsafe_cancel.c')
0 files changed, 0 insertions, 0 deletions