musl - cluts: Incorrect test expectations in buf module (errno)

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110713135124.GC16618@brightrain.aerifal.cx>
Date: Wed, 13 Jul 2011 09:51:24 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: cluts: Incorrect test expectations in buf module (errno)

Hi,
It seems cluts' buf module is surprised that strerror_r and ttyname_r
did not set errno to ERANGE. However these functions are not specified
to report anything in errno. Instead they return the error code
directly. This is an unfortunate inconsistency created in the early
days of "reentrant" (_r) functions due to confusion over whether errno
could be safely used in multithreaded programs. Note that some other
functions which return error codes directly are:

posix_* (posix_memalign etc.)
pthread_*

Rich

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.