* serial.h (SERIAL_SET_TTY_STATE): Comment return value.
[deliverable/binutils-gdb.git] / gdb / remote-vx.c
index abbd918dfaf9b431458da6ba29c3a506365f25b9..5c1aeaaf0fadc76143fa19f4184b56526cf422b1 100644 (file)
@@ -235,7 +235,7 @@ vx_create_inferior (exec_file, args, env)
   stop_soon_quietly = 0;
 
   /* insert_step_breakpoint ();  FIXME, do we need this?  */
-  proceed(-1, -1, 0);
+  proceed (-1, TARGET_SIGNAL_DEFAULT, 0);
 }
 
 /* Fill ARGSTRUCT in argc/argv form with the arguments from the
@@ -566,8 +566,8 @@ static void
 vx_run_files_info ()
 {
   printf_unfiltered ("\tRunning %s VxWorks process %s", 
-         vx_running? "child": "attached",
-         local_hex_string((unsigned long) inferior_pid));
+                    vx_running ? "child" : "attached",
+                    local_hex_string (inferior_pid));
   if (vx_running)
     printf_unfiltered (", function `%s'", vx_running);
   printf_unfiltered(".\n");
@@ -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;
This page took 0.024094 seconds and 4 git commands to generate.