aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base
diff options
context:
space:
mode:
authorJim Kingdon <jkingdon@engr.sgi.com>1995-01-11 05:53:49 +0000
committerJim Kingdon <jkingdon@engr.sgi.com>1995-01-11 05:53:49 +0000
commit7454930699835d060e8540a29dd51bec06ed2071 (patch)
tree78044feec475b028328f9c027f8a075269af5192 /gdb/testsuite/gdb.base
parent4f9045b47c47ef9b17efd07286b7d646cf454aad (diff)
downloadgdb-7454930699835d060e8540a29dd51bec06ed2071.zip
gdb-7454930699835d060e8540a29dd51bec06ed2071.tar.gz
gdb-7454930699835d060e8540a29dd51bec06ed2071.tar.bz2
* gdb.base/sigall.c (gen_FPE): Generate SIGFPE with kill() rather
than by dividing by zero.
Diffstat (limited to 'gdb/testsuite/gdb.base')
-rw-r--r--gdb/testsuite/gdb.base/sigall.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/sigall.c b/gdb/testsuite/gdb.base/sigall.c
index ba28298..c23d7fe 100644
--- a/gdb/testsuite/gdb.base/sigall.c
+++ b/gdb/testsuite/gdb.base/sigall.c
@@ -486,8 +486,15 @@ gen_FPE ()
do the same for SIGBUS, SIGSEGV, etc., but I suspect that even this
test might turn out to be insufficiently portable. */
+#if 0
+ /* Loses on the PA because after the signal handler executes we try to
+ re-execute the failing instruction again. Perhaps we could siglongjmp
+ out of the signal handler? */
/* The expect script looks for the word "kill"; don't delete it. */
return 5 / x; /* and we both started jumping up and down yelling kill */
+#else
+ kill (getpid (), SIGFPE);
+#endif
}
int