Enrico Migliore wrote: > As far as I can say, the main problem of porting a JVM, designed for > UNIX, to the Windows environment are the ANSI signals: > Windows, in fact, doesn't honor not even a fourth of all ANSI signals, > therefore, the JVM signals handler WILL NOT be called by Windows.
You should try compiling SableVM with: ./configure --with-treading=switch --disable-signals-for-exceptions this will turn on ISO C compatibility and reduce (eliminate?) the use of signals. I think that the only remaining signal handling will be one provided for debugging: dumping a stack trace on SIGQUIT signals. Other POSIX dependencies might persist... See my message on a different thread. Etienne -- Etienne M. Gagnon, Ph.D. http://www.info2.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/
signature.asc
Description: OpenPGP digital signature
