Status: Needs Scheduling
Priority: Minor - P4
Affects Version/s: WT3.2.1, WT10.0.0
Fix Version/s: None
We would like to ask clarification about the "thread-safe" property of WT_SESSION::strerror function.
In the documentation of wiredtiger_strerror there is a note about that the WT_SESSION::strerror maybe thread-safe (both for 3.2.1 and 10.0.1):
(see WT_SESSION::strerror for a thread-safe API).
In the implementation of WT_SESSION::strerror there is a direct call of wiredtiger_strerror. Because of that the WT_SESSION::strerror seems to be not thread-safe.
An example code that demonstrates the problem is the following:
Note that both error strings are the same. If the WT_SESSION::strerror is thread-safe then the expected behavior would be to get the two different error strings ( "Unknown error 2000" and " Unknown error 3000").