RFR(s): 8148425: strerror() function is not thread-safe
volker.simonis at gmail.com
Fri Feb 26 19:00:16 UTC 2016
it's good that somebody finally addresses this long standing issue :)
However I wonder if it would be possible to align this effort with the
core libraries group (CC'ed). They already fix this issue with:
8133249: Occasional SIGSEGV: non thread-safe use of strerr in getLastErrorString
I would be nice if we could use the same version in hotspot and the
On Fri, Feb 26, 2016 at 5:05 PM, Thomas Stüfe <thomas.stuefe at gmail.com> wrote:
> please take a look at this proposed fix:
> Bug: https://bugs.openjdk.java.net/browse/JDK-8148425
> This adds a replacement function os::strerror() as a drop-in for
> strerror(), which has a number of issues.
> strerror() is unsafe to use and may cause (and has caused) crashes in
> multithreaded scenarios. It is also not ideal for log files because of the
> implicit localization of the error messages.
> For details please see the discussion under the bug report.
> Please note that I did not yet change any call sites, although all call
> sites in the os namespace should already use the new function. I wanted to
> see whether there would be any general objections.
> Kind Regards, Thomas
More information about the core-libs-dev