mcs%netscape.com 61b529e662 Fix bug # 179951 - libprldap "cross thread" memory leak.
The prldap_tsd_destroy() function (which is called when a
	thread exits) was not freeing the information contained within
	the PRLDAP_ErrorInfo structure. Added prldap_free_errorinfo()
	and a way to determine if that thread-private data looks like
	error information (the plei_magic field). At the moment, only
	one kind of thread-private data is stored anyway (the error
	information).

	The prldap_allocate_map() function, which is called when a new
	LDAP session is created, was blindly setting the thread-private
	error information pointer to NULL. But if a different thread
	created or used an LDAP session than called ldap_unbind(), old
	error information may have been left in memory. Now the error
	info. pointer is reset and reused, which was the original goal.
2002-11-14 23:07:27 +00:00
..
2002-04-27 23:41:15 +00:00
2000-10-05 19:47:47 +00:00