NULL out js->expected_rspauth, so it doesn't get double-freed in jabber_close().

Fri, 23 May 2008 14:58:39 +0000

author
Will Thompson <resiak@pidgin.im>
date
Fri, 23 May 2008 14:58:39 +0000
changeset 23265
c7359dde8a1b
parent 23264
590c2b4ab42f
child 23266
4abc3fc944da

NULL out js->expected_rspauth, so it doesn't get double-freed in jabber_close().
It is still freed in jabber_close() if not NULL, in case the challenge-response
had not completed when the connection is closed.

libpurple/protocols/jabber/auth.c file | annotate | diff | comparison | revisions
--- a/libpurple/protocols/jabber/auth.c	Fri May 23 13:39:22 2008 +0000
+++ b/libpurple/protocols/jabber/auth.c	Fri May 23 14:58:39 2008 +0000
@@ -945,6 +945,7 @@
 					_("Invalid challenge from server"));
 			}
 			g_free(js->expected_rspauth);
+			js->expected_rspauth = NULL;
 		} else {
 			/* assemble a response, and send it */
 			/* see RFC 2831 */

mercurial