)]}'
{
  "commit": "53d4a55bebf56c5ceb6bcf7ff43efd05043a0fc7",
  "tree": "dc1ae8a535fbb73417f16d1cca244d9575988881",
  "parents": [
    "8d215439f665e51adc55dc2c4ba743ee576cb2fc"
  ],
  "author": {
    "name": "Bruno Larsen",
    "email": "blarsen@redhat.com",
    "time": "Wed Jul 20 16:44:38 2022 -0300"
  },
  "committer": {
    "name": "Bruno Larsen",
    "email": "blarsen@redhat.com",
    "time": "Thu Sep 22 11:04:18 2022 +0200"
  },
  "message": "fix gdb.base/jit-elf.exp when testing with clang\n\nWhen using clang as the compiler for the target, gdb.base/jit-elf.exp\nwas failing because the filename displayed when GDB attached to the\ninferior was only showing up as with a relative path, like so:\n\n       (gdb) attach 3674146\n       Attaching to program: /home/blarsen/Documents/gdb-build/gdb/testsuite/outputs/gdb.base/jit-elf/jit-elf-main, process 3674146\n       Reading symbols from /lib64/libm.so.6...\n       Reading symbols from .gnu_debugdata for /lib64/libm.so.6...\n       (No debugging symbols found in .gnu_debugdata for /lib64/libm.so.6)\n       Reading symbols from /lib64/libc.so.6...\n       (No debugging symbols found in /lib64/libc.so.6)\n       Reading symbols from /lib64/ld-linux-x86-64.so.2...\n       [Thread debugging using libthread_db enabled]\n       Using host libthread_db library \"/lib64/libthread_db.so.1\".\n       0x00000000004013ff in main (argc\u003d3, argv\u003d0x7fffffffd820) at ../../../common/git-repos/binutils-gdb/gdb/testsuite/gdb.base/jit-elf-main.c:118\n       118|  WAIT_FOR_GDB; i \u003d 0;  /* gdb break here 1 */\n       (gdb) FAIL: gdb.base/jit-elf.exp: attach: one_jit_test-2: break here 1: attach\n\nWhile gcc\u0027s output is as follows:\n\n       (gdb) attach 3592961\n       Attaching to program: /home/blarsen/Documents/gdb-build/gdb/testsuite/outputs/gdb.base/jit-elf/jit-elf-main, process 3592961\n       Reading symbols from /lib64/libm.so.6...\n       Reading symbols from .gnu_debugdata for /lib64/libm.so.6...\n       (No debugging symbols found in .gnu_debugdata for /lib64/libm.so.6)\n       Reading symbols from /lib64/libc.so.6...\n       (No debugging symbols found in /lib64/libc.so.6)\n       Reading symbols from /lib64/ld-linux-x86-64.so.2...\n       [Thread debugging using libthread_db enabled]\n       Using host libthread_db library \"/lib64/libthread_db.so.1\".\n       main (argc\u003d3, argv\u003d0x7fffffffd860) at /home/blarsen/Documents/gdb-build/gdb/testsuite/../../../common/git-repos/binutils-gdb/gdb/testsuite/gdb.base/jit-elf-main.c:118\n       118|  WAIT_FOR_GDB; i \u003d 0;  /* gdb break here 1 */\n       (gdb) PASS: gdb.base/jit-elf.exp: attach: one_jit_test-2: break here 1: attach\n\nThis difference only happens when GDB\u0027s configure is ran using a\nrelative path, but seeing as testing the full path is not important for\nthis specific test, it feels worth fixing anyway.  To fix the false\npositive, the regexp for checking where gdb has stopped was relaxed a\nlittle to allow the relative path.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "38d541f74b99481d206a75217e23807f61d79835",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/jit-elf.exp",
      "new_id": "0753072974f63dc37ea05155c581fdfdf3c6a3a1",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/jit-elf.exp"
    }
  ]
}
