Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 08 Feb 2013 18:30:00 +0100
From: Jens Gustedt <>
Subject: Re: guard bug for strerror_r

Am Freitag, den 08.02.2013, 17:55 +0100 schrieb Szabolcs Nagy:
> musl provides the posix api when requested
> musl provides many gnu specific apis when _GNU_SOURCE is set
> but when posix and gnu collides it's always the posix api,

definitively a good strategy, but which reaches its limits, here.

> musl never provides broken gnu apis
> at least this was the policy so far

__GNU_SOURCE is defined by the gnu platform to specify the
availability of their extensions. Unfortunately they don't have a
finer grained tool to distinguish different types of extensions they
provide. (BTW the same holds for gcc, that you only can tune with
version numbers.)

If I, as a user, define __GNU_SOURCE I expect to have the gnu
extension, if I then use strerror_r I expect to have their interface,
since this is documented like this. At least as it is now, I don't
think I have any means to distinguish the two platforms and to know
which version of strerror_r I would receive.


:: INRIA Nancy Grand Est ::   ::
:: AlGorille ::::::::::::::: office Nancy : +33 383593090   ::
:: ICube :::::::::::::: office Strasbourg : +33 368854536   ::
:: ::::::::::::::::::::::::::: gsm France : +33 651400183   ::
:: :::::::::::::::::::: gsm international : +49 15737185122 ::

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)

Powered by blists - more mailing lists

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