nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-04-11 08:08:06 -05:00
Code Issues Projects Releases Wiki Activity

Remove the diagnostic added in rev 1.42 [r2288]; apparently it's all

Browse Source 
true and WinSock _does_ occasionally send us netevent messages with
no socket for no reason. Ignore them when they appear.

[originally from svn r2518]
[r2288 == 3bb2e4568c15f5cd76544772ec20f337b8ffb8d5]
This commit is contained in:
Simon Tatham 2003-01-09 19:26:12 +00:00
parent cdec9c7870
commit 1604a192fe
1 changed files with 2 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
winnet.c
View File

@ -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)