JNI Signature Code Analysis

Question

Is there any tool for analyzing static code that detects errors in the JNI (method) signature lines? For example, the following code is not syntactically correct (there is no semicolon after the full class name):

(*env)->GetMethodID(env, someClassId, "aMethod","(ILfoo/bar/TheClass)V"); 

edit: The code analysis tool does not need to check for the existence of foo / bar / TheClass, but only checks the string for valid syntax according to the JNI specification.

This question is based on the fact that the code above caused a segmentation error. This is always an annoying debugging situation, but static analysis should be fairly easy, in this case save a lot of time.

Answer 1

If you only need a static analysis of cases like the one in your question, where the signature is directly inside the GetMethodID call, you can simply write a quick script that looks at the code files and finds all GetMethodID / GetFieldID with a regular expression, and then checks the syntax .

But you can always use -Xcheck:jni ( Oracle / IBM ) to debug these issues. JNI calls will be slower due to validation performed by the JVM, but the required debugging work is greatly reduced.