Add a call to MemoryDebug::MarkAsInitialized to the new network code to avoid...

net/base/tcp_client_socket_win.cc

Index: net/base/tcp_client_socket_win.cc
===================================================================
--- net/base/tcp_client_socket_win.cc	(revision 6529)
+++ net/base/tcp_client_socket_win.cc	(working copy)
@@ -4,6 +4,7 @@
 
 #include "net/base/tcp_client_socket.h"
 
+#include "base/memory_debug.h"
 #include "base/string_util.h"
 #include "base/trace_event.h"
 #include "net/base/net_errors.h"
@@ -175,6 +176,14 @@
     BOOL ok = WSAResetEvent(overlapped_.hEvent);
     CHECK(ok);
     TRACE_EVENT_END("socket.read", this, StringPrintf("%d bytes", num));
+
+    // Because of how WSARecv fills memory when used asynchronously, Purify
+    // isn't able to detect that it's been initialized, so it scans for 0xcd
+    // in the buffer and reports UMRs (uninitialized memory reads) for those
+    // individual bytes. We override that in PURIFY builds to avoid the false
+    // error reports.
+    // See http://code.google.com/p/chromium/issues/detail?id=5297

[darin (slow to review), 2008/12/10 17:33:29]

Can we use a more abbreviated way of referring to DIT issues?  How about
http://crbug.com/5297 or just bug 5297 since we have b/12345678 for buganizer
references?

+    base::MemoryDebug::MarkAsInitialized(buffer_.buf, num);
     return static_cast<int>(num);
   }
   int err = WSAGetLastError();