Tjark Weber wrote:
I've noticed some strange behavior of PolyML 4.2.0 for i386/Linux with respect to signals and signal handlers.
Basically, what happens is that after installing my own signal handler for (in my case) the ALRM signal, committing the database, and restarting PolyML, further signals are apparently not delivered anymore, even though the handler itself is installed properly.
Can anyone confirm this behavior, or even better yet, does anyone have an explanation? Maybe I'm just overlooking the obvious.
Tjark, This turned out to be a bug. SIGALRM is used internally by the Poly/ML run-time system so it's supposed to be handled specially. It was handled correctly when it was set up the first time but not when it was set up when the database was reloaded. I've fixed this in CVS on sourceforge (in the "driver" part).
David.