Re: [musl] ✘strerror_r() bug in musl

["Gary E. Miller" <gem@rellim.com>]

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

Yo Wolf!

On Wed, 13 Apr 2022 01:16:34 +0200
Wolf <wolf@wolfsden.cz> wrote:

> On 2022-04-12 14:07:24 -0700, Gary E. Miller wrote:
> > If you gonna leave the code as is, then fix the doc.  gpsd has
> > struggled with this bug for years until I tracked it down.  
> 
> How did you even managed to compile it when the function returned int
> instead of char*? Hard to believe the compiler did not complain...

It compiles fine, and runs fine, until it crashes.  The return value
was never used, so no warning generated.  The three variants
of strerror_r() differ in more than just their return value.

Yes, I know, sloppy, which is why I'm trying to problems like this one.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 851 bytes --]