-   General (
-   -   Causing signals. (

stf92 03-23-2013 02:06 PM

Causing signals.
Hi: Please read this:

      Most process signals (not system signals SIGKILL, SIGSTOP, SIGCONT) are
      mapped to maskable interrupts. There are six  exceptions:  SIGTERM  and
      SIGHUP  will  terminate  z80-mon,  SIGABRT  will  set  the CPU-wait pin
      active, SIGUSR1 will cause a reset and SIGUSR2 will cause a NMI. Lastly
      SIGTRAP  will force the CPU immediately to dump its state into the file
      .CPU.  This enables online monitoring of the running CPU.

According to this, what signals could I use to cause a maskable interrupt and how do I produce the signal?

Pressing ^C I know I generate SIGINT. But the monitor program, the one whose manual I quote above, is executing a Z80 halt instruccion and then locks the keyboard. Any other means to generate SIGINT?

smallpond 03-23-2013 03:58 PM

To get a list of signals, type on a command-line:

kill -l
kill may be used to generate any signal.

stf92 03-23-2013 04:17 PM

Never suspected that. Thanks.

All times are GMT -5. The time now is 11:54 PM.