From: Jeff Law <law@redhat.com>
Date: Tue, 25 Jul 1995 08:52:39 +0000 (+0000)
Subject: 	* gdb.base/signals.exp: Disable whole file for lynx until
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=8b67f01dffbeecf4860c3a6eaf29f26e40ee2424;p=binutils-gdb.git

	* gdb.base/signals.exp: Disable whole file for lynx until
	further notice.

Looks like a bug in the lynx2.2.2 kernel scroggs the stack pointer in
these tests leading to massive failures.  I've sent a nice small concise
example to Mark Rome @ lynx.  Severe braindamage.
---

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index f1b06e64fab..acae380fc23 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,8 @@
 Tue Jul 25 01:03:52 1995  Jeff Law  (law@snake.cs.utah.edu)
 
+	* gdb.base/signals.exp: Disable whole file for lynx until
+	further notice.
+
 	* gdb.base/signals.exp: xfail test where "next" acts like
 	"continue" for lynx.
 
diff --git a/gdb/testsuite/gdb.base/signals.exp b/gdb/testsuite/gdb.base/signals.exp
index 9fe42bc9e17..d7e831e3f0c 100644
--- a/gdb/testsuite/gdb.base/signals.exp
+++ b/gdb/testsuite/gdb.base/signals.exp
@@ -251,6 +251,15 @@ if {[ istarget "m68*-motorola-*" ] || [ istarget "hppa*-*-bsd*" ] ||
   return 0
 }
 
+# lynx2.2.2 doesn't lose signals, instead it screws up the stack pointer
+# in some of these tests leading to massive problems.  I've
+# reported this to lynx, hopefully it'll be fixed in lynx2.3.
+# Severe braindamage.
+if [ istarget "*-*-*lynx*" ] then {
+  setup_xfail "*-*-*"
+  fail "kernel scroggs stack pointer in signal tests on this target"
+}
+
 gdb_exit
 gdb_start