aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorFred Fish <fnf@specifix.com>1996-03-28 00:27:33 +0000
committerFred Fish <fnf@specifix.com>1996-03-28 00:27:33 +0000
commit06f4dc08823ef624e2f8f0713f3b1252b70d1c31 (patch)
tree0e678c16b82747ca1b1d8bbd0cbc791714e1b38b /gdb
parentd3e572fefc2e912a649512738e34a355a53603c9 (diff)
downloadgdb-06f4dc08823ef624e2f8f0713f3b1252b70d1c31.zip
gdb-06f4dc08823ef624e2f8f0713f3b1252b70d1c31.tar.gz
gdb-06f4dc08823ef624e2f8f0713f3b1252b70d1c31.tar.bz2
Note that failures under linux for backtrace through signal handler
are not consistent among different systems, or even the same system.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/gdb.base/a1-selftest.exp4
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/a1-selftest.exp b/gdb/testsuite/gdb.base/a1-selftest.exp
index e431924..f8718b0 100644
--- a/gdb/testsuite/gdb.base/a1-selftest.exp
+++ b/gdb/testsuite/gdb.base/a1-selftest.exp
@@ -455,6 +455,10 @@ GDB.*Copyright \[0-9\]+ Free Software Foundation, Inc..*$prompt $"\
}
# get a stack trace
+ #
+ # This fails on some linux systems for unknown reasons. On the
+ # systems where it fails, sometimes it works fine when run manually.
+ # The testsuite failures may not be limited to just aout systems.
setup_xfail "i*86-*-linuxaout"
set description "backtrace through signal handler"
send "backtrace\n"