Re: [PATCH 2/3] Have different definitions of __pthread_tsd_main agree in size

[Jens Gustedt <jens.gustedt@inria.fr>]

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

Am Montag, den 11.02.2013, 15:39 +0100 schrieb Szabolcs Nagy:
> * Jens Gustedt <jens.gustedt@inria.fr> [2013-02-11 15:07:28 +0100]:
> > So it would at least be good that the internal use of it in musl would
> > be consistent and the C library would not see two distinct objects.
> > 
> 
> no

I take it that this "no" is only for the second part of the
assertion, and that you would subscribe to the shortend phrase

   So it would at least be good that the internal use of it in musl
   would be consistent.

If it is stated in POSIX that a userspace environ is a different
object from the one in the library, I am perfectly fine with
that. Documented behavior is a good thing, and userspace should see
its environ.

As it is currently, without my patch, execv would see __environ and
execvp would see the user space environ. I am still convinced that
this isn't desirable, both should see __environ, and that is what I
meant with my subphrase "and the C library would not see two distinct
objects".

Jens

-- 
:: INRIA Nancy Grand Est :: http://www.loria.fr/~gustedt/   ::
:: AlGorille ::::::::::::::: office Nancy : +33 383593090   ::
:: ICube :::::::::::::: office Strasbourg : +33 368854536   ::
:: ::::::::::::::::::::::::::: gsm France : +33 651400183   ::
:: :::::::::::::::::::: gsm international : +49 15737185122 ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]