)]}'
{
  "commit": "359efc2d894609fcffd24acaf5b35ecb7c8cbc1e",
  "tree": "412ae1c70be5630dd89d6888cb2e0a6400f93f92",
  "parents": [
    "d4c4a2298cad06ca71cfef725f5248f68205f0be"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Apr 07 19:25:26 2022 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Thu Apr 07 19:25:26 2022 +0200"
  },
  "message": "[gdb/testsuite] Make gdb.base/annota1.exp more robust\n\nOn openSUSE Tumbleweed I run into:\n...\nFAIL: gdb.base/annota1.exp: run until main breakpoint (timeout)\n...\n\nThe problem is that the libthread_db message occurs at a location where it\u0027s\nnot expected:\n...\nStarting program: outputs/gdb.base/annota1/annota1 ^M\n^M\n^Z^Zstarting^M\n^M\n^Z^Zframes-invalid^M\n[Thread debugging using libthread_db enabled]^M\nUsing host libthread_db library \"/lib64/libthread_db.so.1\".^M\n^M\n^Z^Zbreakpoints-invalid^M\n^M\n...\n\nFix this by making the matching more robust:\n- rewrite the regexp such that each annotation is on a single line,\n  starting with \\r\\n\\032\\032 and ending with \\r\\n\n- add a regexp variable optional_re, that matches all possible optional\n  output, and use it as a separator in the first part of the regexp\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c9544eec0ec1701b57979c2c3a2b5beb35f76c9f",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/annota1.exp",
      "new_id": "40a13e7cf19033f3dce92a4c4c767fa4a6128646",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/annota1.exp"
    }
  ]
}