> Currently i have to develop an application that is based on a C++ Core.
> For testing purpose i just called some C++-Functions that simply do some
> cout stuff from within a selfwritten Java-GUI. The functions are called
> succesfully but if i want proceed in the Java-Programm i ALWAYS get an:
> SIGSEGV 11* segmentation violation
> stackbase=0x413c5000, stackpointer=0x413c4a28
>
> Full thread dump:
> "Thread-5" (TID:0x4065e658, sys_thread_t:0x414fef04, state:MW) prio=5
> [...and so on...]
>
> The same kind of error happens also with a different C++ Library
> but similar calls (it doesn't matter if the c++ calls are doing some cout
> stuff ore anything else).
> The C++ Calls are compiled with g++ 2.7.2 with the -shared switch.
> The same type of Code (Java and C++) runs without any problems on a Sun
> Solaris 2.5.1 System (also with gcc 2.7.2).
>
> So my conclusion is that there is a (are some) serious bug(s) in the Java
> Native Interface of the JDK-Linux-Port...
> Does anyone have the same kind of problem with jdk1.1.6v2 and JNI Calls
> (calls of C++ Methods from Java) or does anyone have some further
> information or hints for me what to do ?
>
I forgot to mention that i am using the jdk-1.1.6 libc Version
(libc.so.5.4.44) !
Another conspicuous point is that i also get an
SIGSEGV 11*segmentation violation
stackbase=0x413c5000, stackpointer=0x413c4cbc
[...]
when i do certain thread synchronisation/processing like
t1.start();
t2.start();
t1.join();
t2.destroy();
t1 and t2 are two simple Threads: t1 simply calls the sleep()-Method
and t2 simply Pop up an Dialog as long as t1 is sleeping.)
Any suggestions ?
mfg.
Steffen Tacke
