)]}'
{
  "commit": "5e1c53a4427d65fa5d7798aea3893dc64572717e",
  "tree": "f255d4156ab57b5b9b0b22d9227aea3e609767f6",
  "parents": [
    "bbad9f255d76cf7dcd11d15800e508d9849826af"
  ],
  "author": {
    "name": "Joshua Peraza",
    "email": "jperaza@chromium.org",
    "time": "Thu Feb 20 18:56:04 2020 -0800"
  },
  "committer": {
    "name": "Joshua Peraza",
    "email": "jperaza@chromium.org",
    "time": "Fri Feb 21 04:06:35 2020 +0000"
  },
  "message": "android: truncate lower of two overlapping modules\n\nPreviously, the processor truncated the upper of two\noverlapping module ranges to compensate for incorrect\nreporting of module ranges by the Breakpad client.\nCrashpad correctly reports module load ranges, so\nthis truncation strategy is no longer necessary.\n\nHowever, when partitioned libraries are used, the base\nlibrary may have a range which encompasses the other\npartitions. When this is combined with the truncate\nupper merge strategy, the base library\u0027s executable\nsegment is truncated causing symbolization failures.\n\nThis patch changes Android\u0027s merge strategy to truncate\nthe lower range (which is still the base library, but\nthis strategy truncates from the high end of the\nlibrary\u0027s range, instead of its base).\n\nBug: b/149845120\nChange-Id: Ic75ecd3e919432690740eb21ebd4265fc0bbaa86\nReviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2067952\nReviewed-by: Mark Mentovai \u003cmark@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "75b6b455096a7c820e59f75d9ea648bb2250d05c",
      "old_mode": 33188,
      "old_path": "src/processor/minidump.cc",
      "new_id": "f0075eb22df496cf43e13effe42202caadcdd31d",
      "new_mode": 33188,
      "new_path": "src/processor/minidump.cc"
    }
  ]
}