)]}'
{
  "commit": "f0bbba7886f5dba158a143bebbd0691591f22b9f",
  "tree": "904ef6b41ed74b7c34f1987ff4c8fff5a67f5449",
  "parents": [
    "7b9f73fad09a5ec76002625d562e32c4debc2a5e"
  ],
  "author": {
    "name": "Simon Marchi",
    "email": "simon.marchi@efficios.com",
    "time": "Tue Nov 02 15:05:39 2021 -0400"
  },
  "committer": {
    "name": "Simon Marchi",
    "email": "simon.marchi@polymtl.ca",
    "time": "Tue Nov 09 11:15:40 2021 -0500"
  },
  "message": "gdb.debuginfod/fetch_src_and_symbols.exp: fix when GDB is built with AddressSanitizer\n\nThis test fails for me, showing:\n\n    ERROR: tcl error sourcing /home/smarchi/src/binutils-gdb/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp.\n    ERROR: This GDB was configured as follows:\n       configure --host\u003dx86_64-pc-linux-gnu --target\u003dx86_64-pc-linux-gnu\n                 --with-auto-load-dir\u003d$debugdir:$datadir/auto-load\n                 --with-auto-load-safe-path\u003d$debugdir:$datadir/auto-load\n    ... and much more ...\n\nThe problem is that TCL\u0027s exec throws an error as soon as the exec\u0027ed\nprocess outputs on stderr.  When GDB is built with ASan, it prints some\nwarnings about pre-existing signal handlers:\n\n    warning: Found custom handler for signal 7 (Bus error) preinstalled.\n    warning: Found custom handler for signal 8 (Floating point exception) preinstalled.\n    warning: Found custom handler for signal 11 (Segmentation fault) preinstalled.\n\nPass --quiet to GDB to avoid these warnings.\n\nChange-Id: I3751d89b9b1df646da19149d7cb86775e2d3e80f\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "92f3cd8b01dd6f7a0aca9de4d46c09c040a5ff8f",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp",
      "new_id": "31e9e4a92f0c37039a62957162c74498443cf0c5",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp"
    }
  ]
}