* remote-vx.c (vx_wait): Only call i960_fault_to_signal if I80960
authorJim Kingdon <jkingdon@engr.sgi.com>
Thu, 13 Jan 1994 23:06:03 +0000 (23:06 +0000)
committerJim Kingdon <jkingdon@engr.sgi.com>
Thu, 13 Jan 1994 23:06:03 +0000 (23:06 +0000)
is defined.  Otherwise just report TARGET_SIGNAL_UNKNOWN.

gdb/ChangeLog
gdb/remote-vx.c

index 1c6866fa0d6bee8a6afa788a8fc1ac6a785a1ef4..fa086c63ee6694b8099aef60b44005539ea2d3e5 100644 (file)
@@ -1,5 +1,11 @@
 Thu Jan 13 10:32:38 1994  Jim Kingdon  (kingdon@lioth.cygnus.com)
 
+       * remote-vx.c (vx_wait): Only call i960_fault_to_signal if I80960
+       is defined.  Otherwise just report TARGET_SIGNAL_UNKNOWN.
+
+       * mips-tdep.c (mips_push_arguments): Byteswap struct_addr before
+       writing it.
+
        Add search to target vector (#if 0'd until after 4.12):
        * target.h (to_search, target_search): Add.
        * gdbcore.h, core.c (generic_search): Add.
index 3bcb6807485e267b19a9d0dd71aa02f337150b04..bc67664a1f481a2b9cfe18351bc45feb2dc9e443 100644 (file)
@@ -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;