)]}'
{
  "commit": "9cafb376ebdf0d00a2fc2323e3eef26ccb27fa1d",
  "tree": "079f530fabd471c73cfd727c93a4e762436a8b77",
  "parents": [
    "a5a607b0b01c7022d7ccba282491c40da204cba2"
  ],
  "author": {
    "name": "Nelson Billing",
    "email": "nbilling@google.com",
    "time": "Fri Jun 28 12:07:06 2019 -0700"
  },
  "committer": {
    "name": "Nelson Billing",
    "email": "nbilling@google.com",
    "time": "Fri Jun 28 20:44:55 2019 +0000"
  },
  "message": "Explicitly LoadLibrary dbghelp.dll in symbol converter.\n\n- This is a workaround to an issue with gn/clang build of Windows\nsymbol converter where dbghelp.dll is loaded from system32/syswow64\ninstead of alongside the process exe.\n- Why do we care where dbghelp.dll is loaded from? Two considerations:\n  1. dbghelp.dll will only load symsrv.dll from the directory where it\n  resides.\n  2. symsrv.dll requires a file called \"symsrv.yes\" to be in the\n  directory where it resides in order to work with MS symbol stores.\nTherefore if we load dbghelp.dll from syswow64, then we must also\nensure there is a symsrv.dll and symsrv.yes file in syswow64.\n\nChange-Id: Ia283a2c11e276c855a48157aa7be77897af4b02e\nReviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/1680670\nReviewed-by: Mark Mentovai \u003cmark@chromium.org\u003e\nReviewed-by: Ivan Penkov \u003civanpe@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4b0dcf6eb28e5844f09eef160b045108ed561d7c",
      "old_mode": 33188,
      "old_path": "src/tools/windows/converter/ms_symbol_server_converter.cc",
      "new_id": "2b40faeeb5db6be3c936bacd4ebb07a1eda4f9f7",
      "new_mode": 33188,
      "new_path": "src/tools/windows/converter/ms_symbol_server_converter.cc"
    }
  ]
}