)]}'
{
  "commit": "f3e4716cc534f9521bd97abc400d8e8f0e73ea6a",
  "tree": "33e140f7d30ef54e63703cbd39d5c0cd1249bab2",
  "parents": [
    "ed11fb37b3f3de0f9cf056c9fce76dc7a3cc359d"
  ],
  "author": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Fri Sep 15 19:43:55 2023 +0100"
  },
  "committer": {
    "name": "Pedro Alves",
    "email": "pedro@palves.net",
    "time": "Wed Sep 27 15:28:39 2023 +0100"
  },
  "message": "Fix gdb.threads/pthreads.exp error handling/printing\n\nOn Cygwin, I noticed:\n\n (gdb) PASS: gdb.threads/pthreads.exp: break thread1\n continue\n Continuing.\n pthread_attr_setscope 1: No error\n [Thread 8732.0x28f8 exited with code 1]\n [Thread 8732.0xb50 exited with code 1]\n [Thread 8732.0x17f8 exited with code 1]\n\n Program terminated with signal SIGHUP, Hangup.\n The program no longer exists.\n (gdb) FAIL: gdb.threads/pthreads.exp: Continue to creation of first thread\n\nNote \"No error\" in \"pthread_attr_setscope 1: No error\".  That is a bug\nin the test.  It is using perror, but that prints errno, while the\npthread functions return the error directly.  Fix all cases of the\nsame problem, by adding a new print_error function and using it.\n\nWe now get:\n\n  ...\n  pthread_attr_setscope 1: Not supported (134)\n  ...\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\nChange-Id: I972ebc931b157bc0f9084e6ecd8916a5e39238f5\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e1593e980ea4420ee95cb5372f06fb87f699ad8f",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.threads/pthreads.c",
      "new_id": "547bf0fe3f03f1b30611b43ee8238d40802b209b",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.threads/pthreads.c"
    }
  ]
}