)]}'
{
  "commit": "134ec14b1502f30f0028293b35f57c18e44614d0",
  "tree": "2e103c24cc1623495d9b37f343025317cb3f8fea",
  "parents": [
    "c61b7b7b8ea5e3a55b4642dade4798e5c896df66"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Mar 28 14:18:44 2023 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Mar 28 14:18:44 2023 +0200"
  },
  "message": "[gdb/testsuite] Fix gdb.server/non-existing-program.exp with remote-gdbserver-on-localhost\n\nWith test-case gdb.server/non-existing-program.exp and native, I have reliably:\n...\n(gdb) builtin_spawn gdbserver stdio non-existing-program^M\nstdin/stdout redirected^M\n/bin/bash: line 0: exec: non-existing-program: not found^M\nDuring startup program exited with code 127.^M\nExiting^M\nPASS: gdb.server/non-existing-program.exp: gdbserver exits cleanly\n...\n\nBut with target board remote-gdbserver-on-localhost I sometimes have:\n...\n(gdb) builtin_spawn /usr/bin/ssh -t -l remote-target localhost gdbserver \\\n  stdio non-existing-program^M\nstdin/stdout redirected^M\n/bin/bash: line 0: exec: non-existing-program: not found^M\nDuring startup program exited with code 127.^M\nExiting^M\nConnection to localhost closed.^M^M\nPASS: gdb.server/non-existing-program.exp: gdbserver exits cleanly\n...\nand sometimes the exact same output, but a FAIL instead.\n\nFix this by replacing \"Exiting\\r\\n$\" with \"Exiting\\r\\n\" in the regexps.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "32f27fa2b1cf723355f13adf2af417e3d4fe86ff",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.server/non-existing-program.exp",
      "new_id": "eea1eb1d911010f4eb1b2386421dd1c7e3490974",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.server/non-existing-program.exp"
    }
  ]
}