Re: [PATCH v3 1/4] util: Add thread-safe qemu_strerror() function

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

Re: [PATCH v3 1/4] util: Add thread-safe qemu_strerror() function

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()?

Re: [PATCH v3 1/4] util: Add thread-safe qemu_strerror() function

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

Re: [PATCH v3 1/4] util: Add thread-safe qemu_strerror() function

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