On 2023/04/06 17:57, Alex Bennée wrote:
>
> Yohei Kojima writes:
>
>> On 2023/03/31 4:06, Markus Armbruster wrote:
>>> Yohei Kojima writes:
>>>
Add qemu_strerror() which follows the POSIX specification for
strerror(). While strerror() is not guaranteed to be thread-safe, this
f
Yohei Kojima writes:
> On 2023/03/31 4:06, Markus Armbruster wrote:
>> Yohei Kojima writes:
>>
>>> Add qemu_strerror() which follows the POSIX specification for
>>> strerror(). While strerror() is not guaranteed to be thread-safe, this
>>> function is thread-safe.
>>
>> Why not g_strerror()?
On 2023/03/31 4:06, Markus Armbruster wrote:
> Yohei Kojima writes:
>
>> Add qemu_strerror() which follows the POSIX specification for
>> strerror(). While strerror() is not guaranteed to be thread-safe, this
>> function is thread-safe.
>
> Why not g_strerror()?
>
Because g_strerror() uses m
Yohei Kojima writes:
> Add qemu_strerror() which follows the POSIX specification for
> strerror(). While strerror() is not guaranteed to be thread-safe, this
> function is thread-safe.
Why not g_strerror()?
> This function is added to solve the following issue:
> https://gitlab.com/qemu-project
Add qemu_strerror() which follows the POSIX specification for
strerror(). While strerror() is not guaranteed to be thread-safe, this
function is thread-safe.
This function is added to solve the following issue:
https://gitlab.com/qemu-project/qemu/-/issues/416
Signed-off-by: Yohei Kojima
---
in