aboutsummaryrefslogtreecommitdiff
path: root/gdb/remote-vx.c
diff options
context:
space:
mode:
authorJim Kingdon <jkingdon@engr.sgi.com>1994-01-13 23:06:03 +0000
committerJim Kingdon <jkingdon@engr.sgi.com>1994-01-13 23:06:03 +0000
commitd0acb092fd4929e3d6f0aa15815a98c2195420e3 (patch)
tree0cfcffbacca2fdb0397e542c3e8ee9233586f907 /gdb/remote-vx.c
parent9558d13f844f54928d3912d8c3b76d95cd5bb976 (diff)
downloadgdb-d0acb092fd4929e3d6f0aa15815a98c2195420e3.zip
gdb-d0acb092fd4929e3d6f0aa15815a98c2195420e3.tar.gz
gdb-d0acb092fd4929e3d6f0aa15815a98c2195420e3.tar.bz2
* remote-vx.c (vx_wait): Only call i960_fault_to_signal if I80960
is defined. Otherwise just report TARGET_SIGNAL_UNKNOWN.
Diffstat (limited to 'gdb/remote-vx.c')
-rw-r--r--gdb/remote-vx.c9
1 files changed, 9 insertions, 0 deletions
diff --git a/gdb/remote-vx.c b/gdb/remote-vx.c
index 3bcb680..bc67664 100644
--- a/gdb/remote-vx.c
+++ b/gdb/remote-vx.c
@@ -950,7 +950,16 @@ vx_wait (pid_to_wait_for, status)
break;
case EVENT_SIGNAL:
+#ifdef I80960
status->value.sig = i960_fault_to_signal (rdbEvent.sigType);
+#else
+ /* Back in the old days, before enum target_signal, this code used
+ to add NSIG to the signal number and claim that PRINT_RANDOM_SIGNAL
+ would take care of it. But PRINT_RANDOM_SIGNAL has never been
+ defined except on the i960, so I don't really know what we are
+ supposed to do on other architectures. */
+ status->value.sig = TARGET_SIGNAL_UNKNOWN;
+#endif
break;
} /* switch */
return pid;