>
> It depends upon what you're doing in the signal handler. If you're
> trying to call Xforms routines, you're probably going to lose
> eventually. This is because the signal may have interrupted a system
> call or some critical Xforms function. Trying to make Xforms calls in
> such a case will most likely disarrange things terribly and cause your
> program to either hang or dump core.
>
It 'only' caused the program to hang.
> What you want to do is to register a signal handler with
> fl_add_signal_callback(). When a signal arrives, Xforms will log it
> internally and dispatch the signal handler.
>
That did it. I also had to use fl_app_signal_direct() (because my
program got sometimes intterupted by the signal).
Thank you very much for your help. I already searched hours for
a solution :-(
> Refer to the section on Signals in Appendix A for all the details.
>
The printed manual I have here is obviously a little bit outdated
- I read the manual, but an old one ...
> Stevens, _Advanced Programming in the UNIX Environment_, discusses
> signals and system call interaction in some detail, I believe.
>
You're right. It's also on my desk :-)
Thank you again,
Martin.
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/xforms-archive/