)]}'
{
  "commit": "3ff41cdffade9e7b5a78fa56a43351dbd665df7a",
  "tree": "5f031561651603c92cfc0aed7ad18b5c36f16e28",
  "parents": [
    "d929e40e9aed54ef7cd9f8853a34334f4f3c8f8e"
  ],
  "author": {
    "name": "Austin Clements",
    "email": "austin@google.com",
    "time": "Wed Jan 31 11:55:22 2018 -0500"
  },
  "committer": {
    "name": "Austin Clements",
    "email": "austin@google.com",
    "time": "Wed Jan 31 20:57:52 2018 +0000"
  },
  "message": "runtime: suppress \"unexpected return pc\" any time we\u0027re in cgo\n\nCurrently, gentraceback suppresses the \"unexpected return pc\" error\nfor sigpanic\u0027s caller if the M was running C code.\n\nHowever, there are various situations where a sigpanic is injected\ninto C code that can cause traceback to unwind *past* the sigpanic\nbefore realizing that it\u0027s in trouble (the traceback beyond the\nsigpanic will be wrong).\n\nRather than try to fix these issues for Go 1.10, this CL simply\ndisables complaining about unexpected return PCs if we\u0027re in cgo\nregardless of whether or not they\u0027re from the sigpanic frame. Go 1.9\nnever complained about unexpected return PCs when printing, so this is\nsimply a step closer to the old behavior.\n\nThis should fix the openbsd-386 failures on the dashboard, though this\nissue could affect any architecture.\n\nFixes #23640.\n\nChange-Id: I8c32c1ee86a70d2f280661ed1f8caf82549e324b\nReviewed-on: https://go-review.googlesource.com/91136\nRun-TryBot: Austin Clements \u003caustin@google.com\u003e\nTryBot-Result: Gobot Gobot \u003cgobot@golang.org\u003e\nReviewed-by: Ian Lance Taylor \u003ciant@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2261942ab49e8892b43c9b4b03556bedfaed3c84",
      "old_mode": 33188,
      "old_path": "src/runtime/traceback.go",
      "new_id": "747176c278202757fb62591f2cd0b891570b1818",
      "new_mode": 33188,
      "new_path": "src/runtime/traceback.go"
    }
  ]
}