-
Bug
-
Resolution: Fixed
-
P4
-
11, 17, 20
-
b24
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8342626 | 17.0.14-oracle | Mimoun Ghordou | P4 | Resolved | Fixed | b03 |
| JDK-8343044 | 17.0.14 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
After a JNI call returned, it should be checked whether there is a pending exception. Otherwise, at the moment of the next JNI call, you will receive a warning message.
This rule is obviously not adhered to in src/jdk.jdwp.agent/share/native/libjdwp/util.c. To reproduce, simply issue the command
bin/java -Xcheck:jni -agentlib:jdwp=transport=dt_socket,server=y,suspend=n -version
and you will see the warning.
The rule violation was found with the help of the test
test/jdk/tools/launcher/TestXcheckJNIWarnings.java
using SAP's commercial VM offering. For the OpenJDK variant to show the warning, you will need to specify the above -agentlib parameter.
This rule is obviously not adhered to in src/jdk.jdwp.agent/share/native/libjdwp/util.c. To reproduce, simply issue the command
bin/java -Xcheck:jni -agentlib:jdwp=transport=dt_socket,server=y,suspend=n -version
and you will see the warning.
The rule violation was found with the help of the test
test/jdk/tools/launcher/TestXcheckJNIWarnings.java
using SAP's commercial VM offering. For the OpenJDK variant to show the warning, you will need to specify the above -agentlib parameter.
- backported by
-
JDK-8342626 WARNING: JNI call made without checking exceptions
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Closed
-
- links to
-
Commit
openjdk/jdk/eac26f4e
-
Commit(master)
openjdk/jdk17u-dev/e3e79097
-
Review
openjdk/jdk/11083
-
Review(master)
openjdk/jdk17u-dev/2983
(2 links to)