aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python/py-pp-maint.c
diff options
context:
space:
mode:
authorAndreas Arnez <arnez@linux.vnet.ibm.com>2016-01-20 19:41:45 +0100
committerAndreas Arnez <arnez@linux.vnet.ibm.com>2016-01-20 19:41:45 +0100
commitfd356fa28834fa3a9f22f9157a568264ad045010 (patch)
treef8b704fd70e6e8922f404b0f370e7e311dafdd8e /gdb/testsuite/gdb.python/py-pp-maint.c
parent9df22175e153e1a8784afb85fc24983adf346171 (diff)
downloadbinutils-fd356fa28834fa3a9f22f9157a568264ad045010.zip
binutils-fd356fa28834fa3a9f22f9157a568264ad045010.tar.gz
binutils-fd356fa28834fa3a9f22f9157a568264ad045010.tar.bz2
gnu_vector.exp: Respect `should_kfail' for PR 8549
The gnu_vector test case yields a new FAIL on s390x: FAIL: gdb.base/gnu_vector.exp: verify vector return value It was introduced by commit 77ae9c1933b50 "gdb.base/gnu_vector.exp: Don't test output from the inferior". That commit dropped the special handling for GDB's inability (on some targets) to set the return value. This change re-establishes the logic from before, converting the above FAIL to a KFAIL (PRMS gdb/8549). gdb/testsuite/ChangeLog: * gdb.base/gnu_vector.exp: Re-establish handling for should_kfail when GDB can not set the vector return value. Add more comments for clarification.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-pp-maint.c')
0 files changed, 0 insertions, 0 deletions