)]}'
{
  "commit": "43792b0de4e1f9cbd7f38c00f7150df66b8bddea",
  "tree": "cf3ba73084904eff8d23620778199781fa652be1",
  "parents": [
    "7fe3f841453c46b367aec9a130c3b6e0a580effa"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Oct 07 16:17:35 2022 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Oct 07 16:17:35 2022 +0200"
  },
  "message": "[gdb/testsuite] Fix have_mpx with remote-gdbserver-on-localhost\n\nWith target board remote-gdbserver-on-localhost and gdb.arch/i386-mpx-call.exp\nI run into:\n...\nFAIL: gdb.arch/i386-mpx-call.exp: upper_bnd0: continue to a bnd violation\n...\n\nThis is due to the have_mpx test which should return 0, but instead returns 1\nbecause the captured output:\n...\nNo MPX support\nNo MPX support\n...\ndoes not match the used regexp:\n...\n    set status [expr ($status \u003d\u003d 0) \\\n                   \u0026\u0026 ![regexp \"^No MPX support\\r\\n\" $output]]\n...\nwhich does match the captured output with native:\n...\nNo MPX support^M\nNo MPX support^M\n...\n\nFix this by making the \\r in the regexp optional.\n\nTested on x86_64-linux, with native and target board\nremote-gdbserver-on-localhost.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d60dceffd3f73fd938e96dee0a00c582a0c18f0d",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "99a6de6f7245e1e8e13b2ed1474241c165f4baea",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}