On Wed, 21 May 2025 08:34:21 GMT, Aleksey Shipilev wrote:
> In [JDK-8352533](https://bugs.openjdk.org/browse/JDK-8352533), we print the
> suggestion to use VFORK in jspawnhelper misbehaves. But
> [JDK-8357179](https://bugs.openjdk.org/browse/JDK-8357179) deprecated VFORK!
> So the warning mess
On Wed, 21 May 2025 08:34:21 GMT, Aleksey Shipilev wrote:
> In [JDK-8352533](https://bugs.openjdk.org/browse/JDK-8352533), we print the
> suggestion to use VFORK in jspawnhelper misbehaves. But
> [JDK-8357179](https://bugs.openjdk.org/browse/JDK-8357179) deprecated VFORK!
> So the warning mess
On Wed, 21 May 2025 08:34:21 GMT, Aleksey Shipilev wrote:
> In [JDK-8352533](https://bugs.openjdk.org/browse/JDK-8352533), we print the
> suggestion to use VFORK in jspawnhelper misbehaves. But
> [JDK-8357179](https://bugs.openjdk.org/browse/JDK-8357179) deprecated VFORK!
> So the warning mess
On Wed, 21 May 2025 08:34:21 GMT, Aleksey Shipilev wrote:
> In [JDK-8352533](https://bugs.openjdk.org/browse/JDK-8352533), we print the
> suggestion to use VFORK in jspawnhelper misbehaves. But
> [JDK-8357179](https://bugs.openjdk.org/browse/JDK-8357179) deprecated VFORK!
> So the warning mess
In [JDK-8352533](https://bugs.openjdk.org/browse/JDK-8352533), we print the
suggestion to use VFORK in jspawnhelper misbehaves. But
[JDK-8357179](https://bugs.openjdk.org/browse/JDK-8357179) deprecated VFORK! So
the warning message should actually suggest using FORK. This seems to be in
line wi