gdb.debuginfod/fetch_src_and_symbols.exp: fix when GDB is built with AddressSanitizer
authorSimon Marchi <simon.marchi@efficios.com>
Tue, 2 Nov 2021 19:05:39 +0000 (15:05 -0400)
committerSimon Marchi <simon.marchi@polymtl.ca>
Tue, 9 Nov 2021 16:15:40 +0000 (11:15 -0500)
commitf0bbba7886f5dba158a143bebbd0691591f22b9f
tree904ef6b41ed74b7c34f1987ff4c8fff5a67f5449
parent7b9f73fad09a5ec76002625d562e32c4debc2a5e
gdb.debuginfod/fetch_src_and_symbols.exp: fix when GDB is built with AddressSanitizer

This test fails for me, showing:

    ERROR: tcl error sourcing /home/smarchi/src/binutils-gdb/gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp.
    ERROR: This GDB was configured as follows:
       configure --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
                 --with-auto-load-dir=$debugdir:$datadir/auto-load
                 --with-auto-load-safe-path=$debugdir:$datadir/auto-load
    ... and much more ...

The problem is that TCL's exec throws an error as soon as the exec'ed
process outputs on stderr.  When GDB is built with ASan, it prints some
warnings about pre-existing signal handlers:

    warning: Found custom handler for signal 7 (Bus error) preinstalled.
    warning: Found custom handler for signal 8 (Floating point exception) preinstalled.
    warning: Found custom handler for signal 11 (Segmentation fault) preinstalled.

Pass --quiet to GDB to avoid these warnings.

Change-Id: I3751d89b9b1df646da19149d7cb86775e2d3e80f
gdb/testsuite/gdb.debuginfod/fetch_src_and_symbols.exp