)]}'
{
  "commit": "5f69c00a6e0704627ab1b529d3a2fcdf244da3e8",
  "tree": "bfbfa670b7932669314bf266fd5df1f564731dd6",
  "parents": [
    "43720b0cdd2a2171ef7125bb1572e9daf7d88f07"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Dec 12 09:35:23 2025 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Dec 12 09:35:23 2025 +0100"
  },
  "message": "[gdb/testsuite] Fix timeout in gdb.base/async-shell.exp\n\nFor test-case gdb.base/async-shell.exp, I usually get:\n...\n(gdb) run \u0026^M\nStarting program: async-shell ^M\n(gdb) PASS: $exp: run \u0026\n[Thread debugging using libthread_db enabled]^M\nUsing host libthread_db library \"/lib64/libthread_db.so.1\".^M\nshell echo foo^M\nfoo^M\n(gdb) PASS: $exp: shell echo foo\n...\n\nAnd with taskset -c 11, I get instead:\n...\n(gdb) run \u0026^M\nStarting program: async-shell ^M\n(gdb) PASS: $exp: run \u0026\nshell echo foo^M\nfoo^M\n(gdb) PASS: $exp: shell echo foo\n[Thread debugging using libthread_db enabled]^M\nUsing host libthread_db library \"/lib64/libthread_db.so.1\".^M\n...\n\nWith a gdb 16.3 based package I ran into:\n...\n(gdb) run \u0026\nStarting program: async-shell\n(gdb) PASS: $exp: run \u0026\nshell echo foo\nfoo\n(gdb) [Thread debugging using libthread_db enabled]\nUsing host libthread_db library \"/lib64/libthread_db.so.1\".\nFAIL: $exp: shell echo foo (timeout)\n...\n\nI have tried to reproduce this using various timing tricks, but haven\u0027t\nmanaged.  Nevertheless, I believe this can reproduced with trunk, so fix this\nusing -no-prompt-anchor.\n\nPR testsuite/33667\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d33667\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "228ed10008fa84a5cde98fc0443bcce1d8fb02dd",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/async-shell.exp",
      "new_id": "95d6cc28b99b1f2b9c7f4a09ca24b7d7aa5fee19",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/async-shell.exp"
    }
  ]
}