JDK-8237574 : Make TestNative work without -nativepath
- Type: Bug
- Component: hotspot
- Sub-Component: jfr
- Affected Version: 15
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-01-21
- Updated: 2022-08-18
- Resolved: 2020-01-29
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 15 |
|---|
15 b09Fixed  |
Related Reports
|
Relates :
|
Description
TestNative compiles a JNI method and verifies that a native sample event can be taken. This works well when running tests using 'make test', but is a nuisance when running JFR test from the command line as you need to specify -nativepath or the test fails. Instead of compiling a native method, we could use an already existing native method in the jdk.jfr.JVM class.
Comments
|