)]}'
{
  "commit": "51729ea0905d1f688b7fd2ea769e69b29daa1b7c",
  "tree": "275b0b814fdf6896da6b3f0775af1324ea434835",
  "parents": [
    "f9f033220046f011aeb259469cb15fe8141b213b"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Mar 13 07:49:33 2025 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Mar 13 07:49:33 2025 +0100"
  },
  "message": "[gdb/record] Fix out-of-bounds write in aarch64_record_asimd_load_store\n\nAfter compiling gdb with -fstack-protector-all, and running test-case\ngdb.reverse/getrandom.exp on aarch64-linux, we run into\n\"Stack smashing detected\" in function aarch64_record_asimd_load_store.\n\nThis is reported in PR record/32784.\n\nThis happens due to an out-of-bounds write to local array record_buf_mem:\n...\n  uint64_t record_buf_mem[24];\n...\nwhen recording insn:\n...\nB+\u003e0xfffff7ff4d10  st1     {v0.16b-v3.16b}, [x0]\n...\n\nWe can fix this by increasing the array size to 128, but rather than again\nhardcoding a size, reimplement record_buf_mem as std::vector.\n\nTested on aarch64-linux.\n\nApproved-By: Guinevere Larsen \u003cguinevere@redhat.com\u003e\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d32784\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f8c9fafb229d7c31c730b34b462dce62c8741a38",
      "old_mode": 33188,
      "old_path": "gdb/aarch64-tdep.c",
      "new_id": "bd107b8ce3af5fb03fa8c8be0085ec4729da651f",
      "new_mode": 33188,
      "new_path": "gdb/aarch64-tdep.c"
    }
  ]
}