Hallo Lee,
LX>figure out why. I have a feeling that saving JNIEnv and jobject in so1
LX>to global vars may have problem but not sure. Thank you and forgive me
LX>for
I am no expert on .so's, but "global variables" in conjunction with "dynamic
binding" should ring an alarm bell immediately in any case. ;-) Especially in
YOUR case, where you're loading the same library (so1) twice, once from the
Java side, and once from so2. I would be surprised if both would share the
same global variables (but as I said, I'm no .so expert).
Try to remove any global variables. This will force you to pass them around
more often (especially, into so2 and out of it again), but it may work better
afterwards. If you don't want to include the jni.h in so2, you could pass them
as void* (with explicit casts in so1) and/or create wrapper structs/classes
for them (so that you only need to pass one pointer instead of two).
MbG, Ekkehard
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
