[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: thread specific storage bug?
From: |
Wolfram Gloger |
Subject: |
Re: thread specific storage bug? |
Date: |
Mon, 16 Oct 2000 17:41:16 +0200 (MDT) |
Hello,
> At the point that __pthread_destroy_specifics runs p_terminated is 0.
> So what can occur is that pthread_key_delete can set free'd memory
> to NULL.
I can't see how you can arrange in your program that
pthread_key_delete() is executed _after_ __pthread_destroy_specifics()
has free'd the 1st level keys.
pthread_key_delete() is callable from thread destructor functions,
sure, but __pthread_destroy_specifics() only frees the 1st level keys
_after_ all destructor functions (and hence all possible
pthread_key_delete()'s) have been called.
Can you either explain your problem in more detail or provide a short
test case?
Regards,
Wolfram.