)]}'
{
  "commit": "5ae26f34ef5ac863203d63fffc968d63e823172f",
  "tree": "89b55d6d903982a8d882e5d35b813355227cb57c",
  "parents": [
    "297cd3f78b491c65f05580d78195e5f361fb1a28"
  ],
  "author": {
    "name": "Bratislav Filipovic",
    "email": "bfilipov@amd.com",
    "time": "Fri Apr 03 08:11:02 2026 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Apr 03 08:11:02 2026 +0200"
  },
  "message": "testsuite: ada-valprint-error relocation issue\n\nThe ada-valprint-error.exp test links a nodebug .o file with a separate\nDWARF .o file generated by lib/dwarf.exp. This requires the linker to\napply relocations for initialized pointers in the .data section.\n\nSome clang + linker combinations fail to apply these relocations,\nleaving fd__global as NULL instead of pointing to buffer. This causes\nthe test to print null instead of the expected error message.\n\nBinary evidence from .comment section confirms which compiler and\nlinker were used. Testing shows:\n- GCC 13 + GNU ld 2.42: PASS\n- clang 20 + GNU ld 2.42: FAIL\n- clang 22 + ld.lld 22: FAIL\n- clang 17/19 + GNU ld 2.45.0: PASS\n\nThe failure is a linker limitation when handling this specific\nrelocation pattern, not a GDB bug. Document this in the test file\nto help users understand why the test may fail with certain toolchains.\n\nApproved-By: Tom de Vries \u003ctdevries@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f3d61e91199242ba462df727616d3b84ffd10280",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.dwarf2/ada-valprint-error.exp",
      "new_id": "00e737bcef2baba1305ee83aa95d9c3ec88cb200",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.dwarf2/ada-valprint-error.exp"
    }
  ]
}