sigutil and timer

[Claus Graf]

Hi,

I try to get sigutil working.

At first I tried
ERT HOT_RES(chr$(236), "win1_c68_sigutil")
But if I press ALT F2 a window appears and shortly after that
disappears.
If I try
EW win1_c68_sigutil
I get "bad parameter". I use SMSQ/E 2.98.
What could be the reason?

I also want to program a timer with C68 code.
I read several docs (signal_doc, libc68_doc, UNIX man pages) and it is
quite
confusing IMHO.
Has anyone used the signal extension to make use of the timer
capabilities?
Some code snippets would be welcome.
I tried something like
set_timer_event( &msg)
after setting up the TMR_MSG struct.
Then
io_open("*SIGNAL_R", 0);
new_action.sa_handler = my_handler;
sigaction(msg.signr, &new_action, NULL)
while(1){ /* wait for signals to come */}
I get no error message but also nothing happens.

Thanks

Claus

[Richard Zidlicky]

In <3A473809...@q40.de> Claus Graf <cg...@q40.de> writes:

>Hi,

>I try to get sigutil working.

>At first I tried
>ERT HOT_RES(chr$(236), "win1_c68_sigutil")
>But if I press ALT F2 a window appears and shortly after that
>disappears.
>If I try
>EW win1_c68_sigutil
>I get "bad parameter". I use SMSQ/E 2.98.
>What could be the reason?

In many c68 distributions the dataspace is not set correctly
for sigutil. I assume sigext_rext is loaded at that time?

>I also want to program a timer with C68 code.
>I read several docs (signal_doc, libc68_doc, UNIX man pages) and it is
>quite
>confusing IMHO.
>Has anyone used the signal extension to make use of the timer
>capabilities?
>Some code snippets would be welcome.
>I tried something like
>set_timer_event( &msg)
>after setting up the TMR_MSG struct.
>Then
>io_open("*SIGNAL_R", 0);
>new_action.sa_handler = my_handler;
>sigaction(msg.signr, &new_action, NULL)
>while(1){ /* wait for signals to come */}
>I get no error message but also nothing happens.

Dave built a special optimisation that replaces the whole
signal library with a dummy version unless some standard
function from this library is referenced. Could be alarm()
or something, probably described in TECHREF.doc or somewhere.

Anyway, try it with alarm() first, then see what else could
be the problem. I have tested timer events very extensively
so they worked fine at least in QDOS, will try to find the
test programs. Try your testprogram with a QDOS system.

Bye
Richard