darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

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

Browse source 
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.
This commit is contained in:
Jeff Law 1995-07-25 08:52:39 +00:00
parent 2f11e8d4a6
commit 8b67f01dff
2 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
gdb/testsuite/ChangeLog
View file

@ -1,5 +1,8 @@
Tue Jul 25 01:03:52 1995 Jeff Law (law@snake.cs.utah.edu) 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 * gdb.base/signals.exp: xfail test where "next" acts like
"continue" for lynx. "continue" for lynx.

9
gdb/testsuite/gdb.base/signals.exp
View file

@ -251,6 +251,15 @@ if {[ istarget "m68*-motorola-*" ] || [ istarget "hppa*-*-bsd*" ] ||
return 0 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_exit
gdb_start gdb_start