Avoid freeing the backend in notify_remote_exit(), since that's
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Mon, 17 Nov 2008 18:36:27 +0000 (18:36 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Mon, 17 Nov 2008 18:36:27 +0000 (18:36 +0000)
commitee5e66d8ffb8750a588db17306acfd3193cc10a9
treee0c309b1f2952e197fc0d6f5002272d15dc03312
parent0d13bfcd3dc0eac74361d98a550092ffa054e918
Avoid freeing the backend in notify_remote_exit(), since that's
called from within a backend function which will expect its own
backend pointer to still be valid on return. Instead, move all the
real functionality of notify_remote_exit() out into a GTK idle
function.

git-svn-id: svn://svn.tartarus.org/sgt/putty@8304 cda61777-01e9-0310-a592-d414129be87e
unix/gtkwin.c