Warnings to be fixed - memory acess

Bug #1762817 reported by Jiri Srba on 2018-04-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TAPAAL
Critical
Unassigned

Bug Description

When running on Mac with Java 9 I get the following warnings that should be fixed:

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by dk.aau.cs.util.MemoryMonitor (file:/Users/srba/dev/tapaal-fix-1756865/release-version/) to field java.lang.ProcessImpl.pid
WARNING: Please consider reporting this to the maintainers of dk.aau.cs.util.MemoryMonitor
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Kenneth Yrke Jørgensen (yrke) wrote :

It seems like this might be an unsupported hack: "For example on Macs, it returns java.lang.UnixProcess which has a private field called pid. Using Reflection you can easily get the value of this field. This is admittedly a hack, but it might help. What do you need the PID for anyway?" https://stackoverflow.com/questions/4750470/how-to-get-pid-of-process-ive-just-started-within-java-program/5578924

We need to find a supported way of getting the process PID, but until then I guess I would be safe to ignore the warning.

Changed in tapaal:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers