)]}'
{
  "commit": "f67ddc1be6e447b62c970e372cb6459270a47f53",
  "tree": "6ac5cae6efd1424504b9d190c76aab4663ed5635",
  "parents": [
    "9e6e6a2272c78ab8e975692427c641609c0b4573"
  ],
  "author": {
    "name": "Lancelot SIX",
    "email": "lancelot.six@amd.com",
    "time": "Tue Apr 16 09:26:36 2024 +0100"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Jun 12 14:36:48 2026 +0100"
  },
  "message": "gdb/amd-dbgapi-target: Update xfer_partial to always use dbgapi\n\nOn the Windows platform, the entire \"global\" address space is not\nmapped in the inferior memory.  For such configuration, part of the\nglobal address space lives in GPU memory, and can only be accessed via\nrocm-dbgapi.\n\nThis patch updates amd_dbgapi_target::xfer_partial so it always calls\ninto amd-dbgapi to access the global address space.  GDB will still be\ncalled to access host memory using xfer_global_memory callback.\n\nTo be sure that the callback request is not routed back to dbgapi, the\nxfer_global_memory callback is modified to route the request to\nwhichever target sits below the amd-dbgapi target on the target stack.\n\nCo-Authored-By: Pedro Alves \u003cpedro@palves.net\u003e\nChange-Id: I2d5ca46edf65e2dec3606d18f7ad1d22d0275a63\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "08f79006d578674df71733472819b358a55c8043",
      "old_mode": 33188,
      "old_path": "gdb/amd-dbgapi-target.c",
      "new_id": "610a484becd517f7619b71b7719372cf18b1ad8e",
      "new_mode": 33188,
      "new_path": "gdb/amd-dbgapi-target.c"
    }
  ]
}