On Thu, Oct 30, 2014 at 06:45:20PM +0100, Gustaf Neumann wrote:

> I agree that the array should be gone after the call of "nsv_unset a".

> The behavior is now fixed in the tip branch on bitbucket.

Excellent, thank you, Gustaf!

I earlier tried some simpler changes in my sandbox (essentially the
approach used in AOLserver 4.0.10), which crashed the server.
Your fix definitely works, but is more complicated than I expected.
When you get a chance, can you say a bit more about how it works?

E.g., what is the clientData for exactly, and why do some functions
need to use it but others do not?  Before calling Tcl_DeleteHashTable()
to remove the nsv array, you do something interesting with BucketIndex()
and an extra round of locking.  Is that due to some new feature that
AOLserver did not have, maybe the mutex timings?

-- 
Andrew Piskorski <a...@piskorski.com>

------------------------------------------------------------------------------
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Reply via email to