[gdb/testsuite] Run two test-cases with ASAN_OPTIONS=verify_asan_link_order=0
authorTom de Vries <tdevries@suse.de>
Tue, 12 Jul 2022 11:58:31 +0000 (13:58 +0200)
committerTom de Vries <tdevries@suse.de>
Tue, 12 Jul 2022 11:58:31 +0000 (13:58 +0200)
commit75948417af8f86d1b9b0e3b51f904e1345927885
tree9a798ff48f9cab0b5356ff4fe27eba590c43a454
parent09559238fdcca6ffa2ddfdd6a89ac919a9ccb80d
[gdb/testsuite] Run two test-cases with ASAN_OPTIONS=verify_asan_link_order=0

When building gdb with -fsanitize=address we run into:
...
builtin_spawn gdb -nw -nx -iex set height 0 -iex set width 0 -data-directory \
  build/gdb/data-directory^M
==10637==ASan runtime does not come first in initial library list; you \
  should either link runtime to your application or manually preload it with \
  LD_PRELOAD.^M
ERROR: GDB process no longer exists
...

Prevent the ASan runtime error by using
ASAN_OPTIONS=verify_asan_link_order=0.  This makes both test-cases pass.

Tested on x86_64-linux.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29358
gdb/testsuite/gdb.base/libsegfault.exp
gdb/testsuite/gdb.threads/attach-slow-waitpid.exp