Hello Timothy
Ezzel a dátummal: Monday 17 March 2008 14.58.56 Timothy Wall ezt írta:
It's possible that the VM itself is playing with signal handlers, but
I don't know why it would use SIGIO. The VM flag "-Xrs" reduces the
use of signal handlers, you might try that.
Also, if you run the VM under strace you might find out where and when
it calls "signal" or "sigaction".
You might also try "signal" (the simpler form of "sigaction") to see
if the behavior is any different.
I checked it, but nothing happened, but document said:
-Xrs
Reduce usage of operating-system signals by Java virtual machine (JVM).
Sun's JVM catches signals to implement shutdown hooks for abnormal JVM
termination. The JVM uses SIGHUP, SIGINT, and SIGTERM to initiate the running
of shutdown hooks. The JVM uses SIGQUIT to perform thread dumps.
Applications that embed the JVM frequently need to trap signals like
SIGINT or SIGTERM, and in such cases there is the possibility of interference
between the applications' signal handlers and the JVM shutdown-hooks
facility.
To avoid such interference, the -Xrs option can be used to turn off the
JVM shutdown-hooks feature. When -Xrs is used, the signal masks for SIGINT,
SIGTERM, SIGHUP, and SIGQUIT are not changed by the JVM, and signal handlers
for these signals are not installed.
So it isn't sense SIGIO dignal.
13 messages in net.java.dev.jna.usersRe: [jna-users] handling serial port ...
.java
