From ce6fcfa5a3e2be7bab633b555ca4f92e2b7ca64c Mon Sep 17 00:00:00 2001 From: simon Date: Thu, 9 Jan 2003 19:26:12 +0000 Subject: [PATCH] Remove the diagnostic added in rev 1.42 [r2288]; apparently it's all true and WinSock _does_ occasionally send us netevent messages with no socket for no reason. Ignore them when they appear. git-svn-id: svn://svn.tartarus.org/sgt/putty@2518 cda61777-01e9-0310-a592-d414129be87e --- winnet.c | 19 ++----------------- 1 file changed, 2 insertions(+), 17 deletions(-) diff --git a/winnet.c b/winnet.c index 0b93fcd2..4bebe6d7 100644 --- a/winnet.c +++ b/winnet.c @@ -973,23 +973,8 @@ int select_result(WPARAM wParam, LPARAM lParam) /* wParam is the socket itself */ - /* - * One user has reported an assertion failure in tree234 which - * indicates a null element pointer has been passed to a - * find*234 function. The following find234 is the only one in - * the whole program that I can see being capable of doing - * this, hence I'm forced to conclude that WinSock is capable - * of sending me netevent messages with wParam==0. I want to - * know what the rest of the message is if it does so! - */ - if (wParam == 0) { - char *str; - str = dupprintf("Strange WinSock message: wp=%08x lp=%08x", - (int)wParam, (int)lParam); - logevent(NULL, str); - connection_fatal(NULL, str); - sfree(str); - } + if (wParam == 0) + return 1; /* boggle */ s = find234(sktree, (void *) wParam, cmpforsearch); if (!s) -- 2.11.0