I have for work to modify an old dll written in 2005 in c++.
I have installed Eclipse Oxygen, cygwin with gcc, gdb and make.
I have searched in many places, made many changes in my project properties but my problem is here anyway : I have 5 errors "Invalid Arguments".
my code :
JNIEXPORT jobjectArray JNICALL Java_core_dll_ModDriver_EtatSupport(JNIEnv * env, jobject o)
const int nbFen = 4;
const char FAR* name = "EtatSupport";
char* fen1 = NULL;
char* fen2 = NULL;
char* fen3 = NULL;
char* fen4 = NULL;
if ( isDllLoaded() )
typedef unsigned char ( __stdcall * Function)( char*, char*, char*, char* );
Function function = (Function)getDllFunction( name );
if ( function != NULL )
char error = function ( fen1, fen2, fen3, fen4 );
std::cout << "echec" << name;
jobjectArray result = env->NewObjectArray( nbFen, env->FindClass("java/lang/String"), NULL );
jstring jfen1 = env->NewStringUTF( fen1 );
jstring jfen2 = env->NewStringUTF( fen2 );
jstring jfen3 = env->NewStringUTF( fen3 );
jstring jfen4 = env->NewStringUTF( fen4 );
env->SetObjectArrayElement( result, 0, jfen1 );
env->SetObjectArrayElement( result, 1, jfen2 );
env->SetObjectArrayElement( result, 2, jfen3 );
env->SetObjectArrayElement( result, 3, jfen4 );
The first thing to realize is that the "Invalid arguments" error you're getting is coming from Eclipse's own code analysis, not from the compiler. It shouldn't actually be blocking you from building or running your code, it's just an annoyance.
Having established that, the cause of this error is usually a problem with the project configuration, and may be specific to the platform, Java version, etc. (I, for example, do not get such errors on this code on Linux, with GCC 6 and Java 8).
As @Msalters already pointed out in a comment, the errors seem to be caused by Eclipse not being able to resolve the type
jsize. To investigate this, I would open up the header
jni.h (you can do via "Open Declaration" on the #include for it), find the definition of
jsize, and see if there's anything there that might indicate why it doesn't resolve. To rectify the problem, you may need to make adjustments to your project configuration such as specifying additional include paths or defining additional macros.