)]}'
{
  "commit": "183bccfce1bf17673bf5f3d42f3ca8daee20ac73",
  "tree": "9168d3023a244ebf16882cd83902ec6e9953127a",
  "parents": [
    "4f165e008d4f0533804ea125e0eae19f1cc12f9d"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Jul 30 21:50:17 2024 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Jul 30 21:50:17 2024 +0200"
  },
  "message": "[gdb/testsuite] Fix regexp in gdb.ada/mi_var_access.exp some more\n\nWhen running test-case gdb.ada/mi_var_access.exp on arm-linux (debian trixie),\nI run into:\n...\nExpecting: ^(-var-create A_String_Access \\* A_String_Access[\n]+)?((\\^done,name\u003d\"A_String_Access\",numchild\u003d\"[0-9]+\",.*|\\^error,msg\u003d\"Value out of range.\".*)[\n]+[(]gdb[)]\n[ ]*)\n-var-create A_String_Access * A_String_Access\n^error,msg\u003d\"Cannot access memory at address 0x4\"\n(gdb)\nFAIL: gdb.ada/mi_var_access.exp: Create varobj (unexpected output)\n...\n\nThis is similar to the problem fixed by commit c5a72a8d1c3 (\"[gdb/testsuite]\nFix regexp in gdb.ada/mi_var_access.exp\").\n\nThe problem in both cases is that we\u0027re printing an uninitialized variable,\nand consequently we can run into various error messages during printing.\n\nFix this as in the other commit, by accepting the error message.\n\nTested on arm-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b71c8f32151ab5575320364f780d566bddeeba74",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.ada/mi_var_access.exp",
      "new_id": "e797a1576cb045683c648663b595671dac8edf84",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.ada/mi_var_access.exp"
    }
  ]
}