)]}'
{
  "commit": "478e490a4df79436d678ca5f5f1d7c7ac7befa79",
  "tree": "cbcc616dd1feaa61f03a193508ecaba1d6d97f34",
  "parents": [
    "1ef44e861d58ba10674f107a79471852fbd27cda"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Mar 03 11:34:53 2020 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Mar 03 11:34:53 2020 +0100"
  },
  "message": "[gdb/testsuite] Fix gdb.mi/gdb2549.exp with check-read1\n\nWhen running gdb.mi/gdb2549.exp with check-read1, we get:\n...\nRunning src/gdb/testsuite/gdb.mi/gdb2549.exp ...\nFAIL: gdb.mi/gdb2549.exp: register values t (timeout)\n...\n\nThe problem is that the command generates a lot of output, which is matched by\na single \u0027.*\u0027:\n...\nmi_gdb_test \"666-data-list-register-values t\" \\\n  \"666\\\\^done,register-values\u003d\\\\\\[\\{number\u003d\\\"$decimal\\\",value\u003d\\\"$binary\\\"\\}.*\\\\\\]\" \\\n  \"register values t\"\n...\n\nFix this by splitting up the matching and calling exp_continue after each\nnumber/value pair.\n\nTested on x86_64-linux with make targets check and check-read1.\n\ngdb/testsuite/ChangeLog:\n\n2020-03-03  Tom de Vries  \u003ctdevries@suse.de\u003e\n\n\t* gdb.mi/gdb2549.exp: Fix \"register values t\" check-read1 timeout.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "73a05d31435009f2adb992c740f674c62a2fd82b",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/ChangeLog",
      "new_id": "0563fec5326da5b9808b9505d9cc82a6538c0b7c",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/ChangeLog"
    },
    {
      "type": "modify",
      "old_id": "0b4cb6be387e94c3fe7519d5e8d2e881c731ddbe",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.mi/gdb2549.exp",
      "new_id": "cc6441c8ec0d4ff74c4b6c6a1930fc91cf273fd1",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.mi/gdb2549.exp"
    }
  ]
}