)]}'
{
  "commit": "957e3edfc02311bffebbea79c2e09f2b7b4cb8cb",
  "tree": "3d53a87cc4abf57927d44e1ccee53028ef0f73d3",
  "parents": [
    "496e01123d85e3a8c3d8fabae11867206e15cc1e"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Sep 05 08:37:30 2025 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Sep 05 08:37:30 2025 +0200"
  },
  "message": "[gdb/testsuite] Fix silent timeout in allow_aarch64_gcs_tests\n\nI noticed on M1 aarch64-linux that test-case\ngdb.testsuite/gdb-caching-proc-consistency.exp took a long time.\n\nI saw lack of progress in gdb.log for proc allow_aarch64_gcs_tests.\n\nThis gdb_expect only handles the case that gcs support is detected:\n...\n    gdb_expect {\n        -re \".*$inferior_exited_re normally.*${gdb_prompt} $\" {\n            verbose -log \"\\n$me: gcs support detected\"\n            set allow_gcs_tests 1\n        }\n    }\n...\nbut in my case, I get:\n...\n(gdb) run ^M\nStarting program: allow_aarch64_gcs_tests.x ^M\n[Thread debugging using libthread_db enabled]^M\nUsing host libthread_db library \"/lib64/libthread_db.so.1\".^M\n[Inferior 1 (process 3336556) exited with code 01]^M\n(gdb)\n...\nso the gdb_expect times out quietly, taking 10 seconds.\n\nIn the test-case, it does so 11 times.\n\nFix this by adding a gdb_expect clause handling the \"with code 01\" case.\n\nTested on aarch64-linux.\n\nPR testsuite/33378\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d33378\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fe4178ebba79fb2ff6b6c9730c2641e1ea347aa4",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "e67779a26087266e5cc607a00a6d878b47eb98aa",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}