summaryrefslogtreecommitdiffstats
path: root/src/lib/gssapi/generic/util_buffer.c
diff options
context:
space:
mode:
authorJeffrey Altman <jaltman@secure-endpoints.com>2007-06-22 18:58:09 +0000
committerJeffrey Altman <jaltman@secure-endpoints.com>2007-06-22 18:58:09 +0000
commitb3ce9032f0a19eaab43c3bbccb3bfc63635292ae (patch)
tree6b3b5aaabe7cf264e11a1d46312b6d3b56053546 /src/lib/gssapi/generic/util_buffer.c
parent2edfc72bab12e4f7c745184e7795b60f7b567527 (diff)
downloadkrb5-b3ce9032f0a19eaab43c3bbccb3bfc63635292ae.tar.gz
krb5-b3ce9032f0a19eaab43c3bbccb3bfc63635292ae.tar.xz
krb5-b3ce9032f0a19eaab43c3bbccb3bfc63635292ae.zip
Don't assume that WM_DESTROY is the last message to be received by a
window. Since the child windows are still alive and kicking by the time the parent receives WM_DESTROY, it's still possible to receive other messages after WM_DESTROY. If we free any window specific data when handling WM_DESTROY, we should reset the window data field as well, and check if we have a valid pointer when retrieving the window data field later. ticket: 5584 git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@19627 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/lib/gssapi/generic/util_buffer.c')
0 files changed, 0 insertions, 0 deletions