Speculatively back out r984. See http://codereview.chromium.org/10805065/

and
http://build.chromium.org/p/chromium/builders/NACL%20Tests%20%28x64%29/builds/34563

chrome src/native_client/tests/inbrowser_crash_test/crash_dump_tester.py says
that the observed failures are a symptom of crash_service.exe itself crashing.


git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@999 4c0a9323-5329-0410-9bdc-e9ce6186880e

1 files changed, 0 insertions, 2 deletions

diff --git a/src/client/windows/crash_generation/crash_generation_server.cc b/src/client/windows/crash_generation/crash_generation_server.cc
index de3d3fce..477973c1 100644
--- a/src/client/windows/crash_generation/crash_generation_server.cc
+++ b/src/client/windows/crash_generation/crash_generation_server.cc
@@ -796,7 +796,6 @@ void CALLBACK CrashGenerationServer::OnDumpRequest(void* context, BOOLEAN) {
   assert(context);
   ClientInfo* client_info = reinterpret_cast<ClientInfo*>(context);
   client_info->PopulateCustomInfo();
-  client_info->PopulateCustomDataStream();
 
   CrashGenerationServer* crash_server = client_info->crash_server();
   assert(crash_server);
@@ -893,7 +892,6 @@ bool CrashGenerationServer::GenerateDump(const ClientInfo& client,
                                         GetCurrentThreadId(),
                                         client_ex_info,
                                         client.assert_info(),
-                                        client.custom_data_stream(),
                                         client.dump_type(),
                                         true,
                                         dump_path);