<br><font size=2 face="sans-serif">We have a Cbc application that is invoked
from Java using the Java Native Interface (JNI).</font>
<br>
<br><font size=2 face="sans-serif">We're working under Linux.</font>
<br>
<br><font size=2 face="sans-serif">We build a shared-object (.so) library
which provides an entry-point very much like driver4's "main".
This entry works fine when called straight from C++ code. But
when called via JNI it fails in a weird way. It throws a segmentation
fault immediately after entering the function CbcMain1. I moved debugging
statements around the entry to CbcMain1, and I can't resolve the place
the fault is signalled: it looks like it happens as part of the calling
sequence to CbcMain1.</font>
<br>
<br><font size=2 face="sans-serif">A call to CbcMain0, a few lines upstream,
completes successfully.</font>
<br>
<br><font size=2 face="sans-serif">Has anyone else succeeded in using Cbc
from Java/JNI, and do you have any advice to offer? I am suspecting
that some of the compilation flags in the Cbc build process violate JNI's
expectations about library structure, but this vague suspicion doesn't
explain why CbcMain0 works and CbcMain1 fails.</font>