Re: Unicode allowables in Environment variables

[William DeShazer <earl.deshazer@xxxxxxxxx>]

Please educate me if I am wrong about Valgrind, but I believe the reason that Valgrind didn’t catch it is that without asserting that you expect to get out the value you put in, to something like Valgrind nothing bad happened. Munging a variable for all it knows is what you intended to do. As you pointed out earlier, you can still access the variable with printenv. So the munged variable only hides access to the original. In that regard it is not leaking either, or it is leaking the same amount to the same variable, because you can still find it.

This was probably missed because few are bold (stupid?) enough to put non-portable Unicode in their path.

> On Nov 4, 2024, at 15:52, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> 
> On Mon, Nov 4, 2024 at 3:46 PM William DeShazer <earl.deshazer@xxxxxxxxx> wrote:
>> 
>> With regard to your Valgrind observation, I am not surprised. Few people would hazard to put Unicode characters in their path name
> 
> I meant that I specifically tested your example with valgrind, and
> witnessed the problem repeat, without getting any reported errors or
> leaks.