-
Enhancement
-
Resolution: Won't Fix
-
P4
-
7, 8
-
generic
-
generic
A common scenario with native libraries is that a developer introduces or
refactors native code in the libraries, this might introduce a new JNI entry point, and the developer misses adding an entry in the corresponding mapfile, cause the entry to be marked as "LOCAL", ie. private.
This entry point may never be called in the existing regression tests, thus causing
undefined symbols or unsatisfied link errors at execution time.
There needs to be a check in the build infrastructe to ensure that all JNI
entry points and JVM entry points are exported GLOBAL via the mapfile.
refactors native code in the libraries, this might introduce a new JNI entry point, and the developer misses adding an entry in the corresponding mapfile, cause the entry to be marked as "LOCAL", ie. private.
This entry point may never be called in the existing regression tests, thus causing
undefined symbols or unsatisfied link errors at execution time.
There needs to be a check in the build infrastructe to ensure that all JNI
entry points and JVM entry points are exported GLOBAL via the mapfile.
- relates to
-
JDK-8006808 mapfile use check in jdk/make/common/shared/Defs-solaris.gmk is throwing 'egrep: syntax error'
-
- Resolved
-
-
JDK-8017234 Hotspot should stop using mapfiles
-
- Resolved
-
-
JDK-7035109 Regression: awt SplashScreen/test18.sh fails - missing mapfile entry
-
- Closed
-
-
JDK-7033579 XRobotPeer._dispose() native method should be added to the make/sun/xawt/mapfile-vers
-
- Closed
-
-
JDK-8017234 Hotspot should stop using mapfiles
-
- Resolved
-