)]}'
{
  "commit": "ae84e36caf44936ee94d9dcbfe427ff0bd9434df",
  "tree": "59ae5a5a87849ca82ae9be0951d5e96413944a51",
  "parents": [
    "9dd3d66b79a2907726f407039234ad8677e9df16"
  ],
  "author": {
    "name": "Lancelot SIX",
    "email": "lancelot.six@amd.com",
    "time": "Fri Feb 07 11:09:09 2025 +0000"
  },
  "committer": {
    "name": "Lancelot SIX",
    "email": "lancelot.six@amd.com",
    "time": "Fri Feb 07 20:05:33 2025 +0000"
  },
  "message": "gdb/testsuite: fix \"up to main\" in gdb.base/corefile-exec-context.exp\n\nOn ubuntu systems with libc debug info available (libc6-dbg), I see the\nfollowing failures for the gdb.base/corefile-exec-context.exp testcase:\n\n    show args\n    Argument list to give program being debugged when it is started is \"aaaaa bbbbb ccccc ddddd e\\ e\\ e\\ e\\ e\".\n    (gdb) PASS: gdb.base/corefile-exec-context.exp: show args\n    up\n    #1  __pthread_kill_internal (signo\u003d6, threadid\u003d133859295332160) at ./nptl/pthread_kill.c:78\n    78\tin ./nptl/pthread_kill.c\n    (gdb) FAIL: gdb.base/corefile-exec-context.exp: move up to main\n\nThis failures is because the pattern used to parse the output of `up`\nis not expecting what is seen when debugging information is present for\nthose frames.\n\nThis patch adjusts the pattern to allow both possible outputs.\n\nTested on ubuntu-22.04 and ubuntu24.04 with libc6-dbg installed for gdb\nbuild with --with-separate-debug-dir\u003d/usr/lib/debug.\n\nChange-Id: I217d4b20006d0ecdb4b7a71eeb8d01597ec5ac63\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d6d4c0de4bea350868548d9f920499cceb44fd63",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/corefile-exec-context.exp",
      "new_id": "6bd2b04e2a0d2f261bcc306c669a05e86acea904",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/corefile-exec-context.exp"
    }
  ]
}