Fix building ASAN instrumented executables with custom entrypoints

remoting/host/win/entry_point.cc

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include <windows.h>
 
 #include "remoting/host/host_main.h"
 
 // The common entry point for remoting_host.exe and remoting_desktop.exe. In
 // order to be really small the app doesn't link against the CRT.
 void HostEntryPoint() {
   // CommandLine::Init() ignores the passed parameters on Windows, so it is safe
   // to pass nullptr here.
   int exit_code = remoting::HostMain(0, nullptr);
   ExitProcess(exit_code);
 }
+
+#if defined(ADDRESS_SANITIZER)
+// Executables instrumented with ASAN need CRT functions. We do not use
+// the /ENTRY switch for ASAN instrumented executable and a "main" function
+// is required.
+int WINAPI WinMain(HINSTANCE hInstance,

[grt (UTC plus 2), 2017/01/16 15:41:17]

wWinMain here and wmain below -- i think this is built with /DUNICODE like
everything else.

[etienneb, 2017/01/16 16:58:37]

Done.

+                   HINSTANCE hPrevInstance,
+                   LPSTR lpCmdLine,
+                   int nCmdShow) {
+  HostEntryPoint();
+  return 0;
+}
+
+int main() {
+  HostEntryPoint();
+  return 0;
+}
+#endif