Hi All!

I've been working hard to figure out why using the API on Linux with
Java was so unstable and I think today I came up with a fix!  Very
very excited.  In thinking about the signal handlers and exit(1), I
realized that there was an API method called csoundInitialize that one
can init the library to turn off signal handlers and also remove
atexit.  As a test, I initialized the library using this early in blue
before instantiating any Csound instances:

csnd.csnd.csoundInitialize(null, null, csnd.csnd.CSOUNDINIT_NO_SIGNAL_HANDLER);

This turned off installing any signal handlers, and afterwards things
seemed to run well on Linux!  I had noticed when running with
-verbose:jni that there were some warnings reported about signal
handlers installed in Csound and those from the Java Virtual Machine
clashing somewhat.  My guess is that on Linux it's a catastrophic
clash while on Windows it's not a problem.

I am going to test on Fedora next (did my tests on Ubuntu), but am
hopeful this will solve the problem.  I am wondering if it shouldn't
be general advice to do this kind of initialization to turn off
install signal handlers whenever using the Csound API, regardless of
host language.  Thoughts?

Thanks!
steven

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net