aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorFangrui Song <i@maskray.me>2024-01-19 00:39:22 -0800
committerFangrui Song <i@maskray.me>2024-01-19 00:39:23 -0800
commitc875567af352716e703a49c9445f5dc1d3cf0063 (patch)
tree98a63cdd27de988603fec22f8a6f5bd8b8efcb56 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent14f0c06f48aca3e6f015944c88097b404005645e (diff)
downloadllvm-c875567af352716e703a49c9445f5dc1d3cf0063.zip
llvm-c875567af352716e703a49c9445f5dc1d3cf0063.tar.gz
llvm-c875567af352716e703a49c9445f5dc1d3cf0063.tar.bz2
[asan,test] Disable alloca_loop_unpoisoning.cpp on s390{{.*}}
The test (from https://reviews.llvm.org/D7098) is about the interaction of VLA and alloca where the VLA causes alloca to have the same address. This is mostly about behavior checking and less about instrumentation correctness, so I think it is fair to disable it for a platform that does not work after StackSafetyAnalysis is enabled by default (#77210).
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions