)]}'
{
  "commit": "eecab42fb33fcb888fbfdbf457a98a2231fd491e",
  "tree": "14e5f7daf4863df19890a0d1266228144cfb5979",
  "parents": [
    "818ef5f4137aaff3afdb52f8bbd3a4c3a9ffa28b"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Mar 26 17:32:09 2024 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Mar 26 17:32:09 2024 +0100"
  },
  "message": "[gdb/testsuite] Fix valgrind tests on debian\n\nOn debian 12, I run into:\n...\n(gdb) target remote | vgdb --wait\u003d2 --max-invoke-ms\u003d2500 --pid\u003d618591^M\nRemote debugging using | vgdb --wait\u003d2 --max-invoke-ms\u003d2500 --pid\u003d618591^M\nrelaying data between gdb and process 618591^M\nwarning: remote target does not support file transfer, \\\n  attempting to access files from local filesystem.^M\nReading symbols from /lib/ld-linux-aarch64.so.1...^M\n(No debugging symbols found in /lib/ld-linux-aarch64.so.1)^M\n0x000000000401a980 in ?? () from /lib/ld-linux-aarch64.so.1^M\n(gdb) FAIL: gdb.base/valgrind-infcall.exp: target remote for vgdb\n...\n\nThe problem is that we\u0027re expecting to match either of these regexps:\n...\n\tset start_re1 \" in \\\\.?_start \"\n        set start_re2 \"\\\\.?_start \\\\(\\\\) at \"\n...\nbut there are no dwarf or elf symbols present.\n\nFix this by also allowing:\n...\n       set start_re3 \"$::hex in \\\\?\\\\? \\\\(\\\\) from \"\n...\n\nTested on aarch64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2f2d58844f4ab687955b803c031c9261c29aae88",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/valgrind.exp",
      "new_id": "c952e929bae078e68a2def904ac1cdedea3abea9",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/valgrind.exp"
    }
  ]
}