)]}'
{
  "commit": "cbd9efbbc0414b71d47020958b5fbeff25504f15",
  "tree": "f79ce789a36273958c61375bb29a145181889ed5",
  "parents": [
    "389971df23ca74092314dbde1303310a33766ba7"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Wed May 24 17:18:52 2023 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Wed May 24 18:38:03 2023 +0100"
  },
  "message": "gdb/testsuite: fix race in gdb.server/multi-ui-errors.exp\n\nAfter this commit:\n\n  commit ed32754a8c7919feffc6ddb66ff1c532e4a4d1cd\n  Date:   Thu Mar 9 10:45:03 2023 +0100\n\n      [gdb/testsuite] Fix gdb.server/multi-ui-errors.exp for remote target\n\nI noticed the occasional failure in gdb.server/multi-ui-errors.exp,\nwhich looked like this:\n\n  (gdb) PASS: gdb.server/multi-ui-errors.exp: interact with GDB\u0027s main UI\n  interrupt\n  (gdb)\n  Program received signal SIGINT, Interrupt.\n  0x00007ffff7d501e7 in nanosleep () from /lib64/libc.so.6\n  FAIL: gdb.server/multi-ui-errors.exp: interrupt (timeout)\n  PASS: gdb.server/multi-ui-errors.exp: interrupt arrived\n  p server_pid\n  $1 \u003d 718174\n  (gdb) PASS: gdb.server/multi-ui-errors.exp: p server_pid\n\nThis is triggered by this code in gdb.server/multi-ui-errors.exp:\n\n    gdb_test \"interrupt\"\n\n    gdb_test_multiple \"\" \"interrupt arrived\" {\n\t-re \"Program received signal SIGINT, Interrupt\\\\.\\r\\n\" {\n\t    pass $gdb_test_name\n\t}\n    }\n\nThe problem here is that the first interrupt will trigger the prompt\nto be printed, and then, after some time the inferior will be\ninterrupted.\n\nHowever the default pattern for gdb_test includes a \u0027$\u0027 end anchor.\nIf expect sees the prompt with nothing following it then everything is\nfine, and the test passes.\n\nHowever, if the interrupt is quick and so what expect sees is this:\n\n  (gdb)\n  Program received signal SIGINT, Interrupt.\n  0x00007ffff7d501e7 in nanosleep () from /lib64/libc.so.6\n\nIn this case the end anchor means that the gdb_test fails to match,\nand eventually times out.\n\nFix this by passing -no-prompt-anchor to gdb_test.\n\nReviewed-By: Tom de Vries \u003ctdevries@suse.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "af83614fe551d4eefbb1e3fd7229ee61420cb618",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.server/multi-ui-errors.exp",
      "new_id": "47ded35bc8697217c812940d4458b619c919e64a",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.server/multi-ui-errors.exp"
    }
  ]
}