)]}'
{
  "commit": "89525e4ffdf79caefd146dcff8ecd801af7576ae",
  "tree": "b17d8b677dc3b961599b02ea59a2e78241c26921",
  "parents": [
    "9e05bcf99ce772451d9e00eb646296c7c3170c97"
  ],
  "author": {
    "name": "Lancelot SIX",
    "email": "lancelot.six@amd.com",
    "time": "Mon Dec 01 14:29:52 2025 +0000"
  },
  "committer": {
    "name": "Lancelot SIX",
    "email": "lancelot.six@amd.com",
    "time": "Fri Dec 05 10:28:13 2025 +0000"
  },
  "message": "[gdb/testsuite] Use gdb_load in gdb.rocm/break-kernel-no-debug-info.exp\n\nThe gdb.rocm/break-kernel-no-debug-info.exp builds a testcase without\ndebug info, and loads the binary in GDB with:\n\n    gdb_test \"file $::binfile\" \".*No debugging symbols.*\" \"load file\"\n\nOn some configurations (SLES with glibc-devel installed), the compiler\nlinks /usr/lib64/crit1.o (which contains some debug information) into\nthe final binary.  As a result, the binary contains \"some\" debug\ninformation, which makes the above pattern fail.  The testcase is still\nvalid as we only really need the GPU code object (embedded in the main\nbinary) to not contain debug information, so this patch proposes to\nrelax this first step by using \"gdb_load\" instead.\n\nTested on x86_64-linux + AMDGPU gfx1031.\n\nChange-Id: Id903f62e170af69c001b39f4681602a54e2fdaf1\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7773ff31ff0f2736caef85619a1659b337564b09",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.rocm/break-kernel-no-debug-info.exp",
      "new_id": "71c67adbcd655bfed8d19e4e89fc4a3e9acd79d0",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.rocm/break-kernel-no-debug-info.exp"
    }
  ]
}