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.
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.
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