)]}'
{
  "commit": "38b03d23c7c7e6a9f8f27a9899fd0a84587c379e",
  "tree": "4f6454691ffac38a05077f5e0e34b6bf3ab5fc57",
  "parents": [
    "2786ef85faf16c13029548832c4e4b025bf2624c"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Oct 13 11:36:02 2021 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Wed Oct 13 11:36:02 2021 +0200"
  },
  "message": "[gdb/testsuite] Fix gdb.fortran/call-no-debug.exp with native-gdbserver\n\nWhen running test-case gdb.fortran/call-no-debug.exp with target board\nnative-gdbserver, I run into:\n...\n(gdb) PASS: gdb.fortran/call-no-debug.exp: print string_func_ (\u0026\u0027abcdefg\u0027, 3)\ncall (integer) string_func_ (\u0026\u0027abcdefg\u0027, 3)^M\n$2 \u003d 0^M\n(gdb) FAIL: gdb.fortran/call-no-debug.exp: call (integer) string_func_ (\u0026\u0027abcdefg\u0027, 3)\n...\n\nThe problem is that gdb_test is used to match inferior output.\n\nFix this by using gdb_test_stdio.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3c5172e7e36b54ab6777c84b3fc18af4f84e4c2b",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.fortran/call-no-debug.exp",
      "new_id": "cbdefb6a7d9850e7fd43cba87a5a400a0845b6c4",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.fortran/call-no-debug.exp"
    }
  ]
}