)]}'
{
  "commit": "7a8d20b7841b43cc685230058130bd0f019e4004",
  "tree": "7de1a38c0fc21da4d1ed71d4b260aa94e385b863",
  "parents": [
    "ef799d337201e02688c6e07b0cac8912b86f505d"
  ],
  "author": {
    "name": "Saleem Abdulrasool",
    "email": "abdulras@google.com",
    "time": "Wed Jun 08 12:42:23 2022 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed Jun 08 12:43:17 2022 -0700"
  },
  "message": "absl: correct the stack trace path on RISCV\n\nWhen we would perform a stacktrace using the frame pointer walking, because we\ndid the adjustment for the return address separately, we were misaligning the\nstack size and frame.  Simplify the logic and correct the offset.\n\nThe recovered frame pointer provides us with the return address of the current\nframe and the previous frame\u0027s frame pointer.  Subsequently, we decide if we\nwant to record this frame or not.  The value in `next_frame_pointer` already\npoints to the value from the previous stack frame (that is the next frame\npointer to iterate).  As such, the value computed by `ComputeStackFrameSize` is\nthe value for the current frame.  This was offset by one previously.\n\nTake the opportunity to clean up some of the local comments, fixing typos and\nsplitting up the comments to reflect the lines that they are associated with.\n\nPiperOrigin-RevId: 453744059\nChange-Id: If14813e0ac36f327f4b7594472f2222d05c478aa\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "98b09a225601f4c5467721c896c384eb919bbee3",
      "old_mode": 33188,
      "old_path": "absl/debugging/internal/stacktrace_riscv-inl.inc",
      "new_id": "7123b71bc3862da1e813000ae0aeb72525545c17",
      "new_mode": 33188,
      "new_path": "absl/debugging/internal/stacktrace_riscv-inl.inc"
    }
  ]
}