)]}'
{
  "commit": "26a69f095f1a2f534dcd347f28a9282dff0fde1f",
  "tree": "311eac6a5c4d2af411813d4294aea5c282b6d987",
  "parents": [
    "7529ff1fcdbe260a0ac84ee8f33f4fa4ee1ac455"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Mon May 08 15:45:52 2023 -0400"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Thu May 25 08:46:23 2023 -0400"
  },
  "message": "gdb: get gdbarch from syscall_catchpoint instead of location\n\nI noticed some methods of syscall_catchpoint doing this:\n\n  struct gdbarch *gdbarch \u003d loc-\u003eowner-\u003egdbarch;\n\n`loc` is the list of locations of this catchpoint.  Logically, the owner\nthe locations are this catchpoint.  So this just ends up getting\nthis-\u003egdbarch.  Remove the unnecessary indirection through the loc.\n\nsyscall_catchpoint::print_recreate does something slightly different,\ngetting its arch from the loc:\n\n  struct gdbarch *gdbarch \u003d loc-\u003egdbarch;\n\nI suppose it\u0027s always going to be the same arch, so get it from the\ncatchpoint there too.\n\nChange-Id: I6f6a6f8e0cd7cfb754cecfb6249e71ec12ba4855\nReviewed-By: Alexandra Petlanova Hajkova \u003cahajkova@redhat.com\u003e\nReviewed-By: Andrew Burgess \u003caburgess@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d73f6616c97af9a7debe658c3739a04df5e07a88",
      "old_mode": 33188,
      "old_path": "gdb/break-catch-syscall.c",
      "new_id": "595b05c90c8ebf38e56ceaf15251b061ea992ebb",
      "new_mode": 33188,
      "new_path": "gdb/break-catch-syscall.c"
    }
  ]
}