Hmm. Thing is, the stratum code is all done raw now, not using any other libraries precisely because I had problems with libcurl and friends. So the code does raw socket calls which directly use winsock calls. So the problem is either in cgminer or the MS dll.
I hate to be the bearer of bad news, but I doubt it's the winsock dll. A lot of programs use that, and if there was a native problem in there, we'd be getting crashes elsewhere from other apps.
Since you code in linux for linux, and port to Windows, what's doing the conversion of your code to what windows uses? From my experience, problems that make themselves apparent after a period of time indicate a memory leak (a), a multithreaded issue (b), or an unmanaged code issue (c).
(a) should be apparent by increased memory usage or your internal memory leak testing (which I think I've seen you guys say you have)
(b) is awful to troubleshoot. such problems are caused by different multithreading problems like race conditions or deadly embraces
(c) is generally code accessing memory regions that it shouldn't be accessing, like exceeding an array boundary
(b) and (c) are particularly troublesome because the problem may not always cause a symptom and the OS might not always detect it and clamp down on the offending app
third party code analyzers are the best way to spot these for complex code. But if there are third party libraries involved, I doubt the code analyzers would be able to detect such things.
somehow I doubt I'm telling you anything you don't already know though.
M
