|
From: Santeri P. <sa...@ss...> - 2003-08-14 08:10:17
|
Nicholas Nethercote wrote:
>This all sounds very complicated, for a case that comes up very rarely in
>practice. What do you think of just improving the error message produced
>by VG_(mash_LD_PRELOAD_and_LD_LIBRARY_PATH) so it says something like "you
>changed $VG_ARGS, so Valgrind can't continue", and similar for LD_PRELOAD
>and LD_LIBRARY_PATH?
>
>
I agree, this issue is anyway already covered in the FAQ now and I just
stumbled on it because the program I was testing sanitized the
environmental variables for its children.
(I was just pointing out that putenv/clearenv/setenv are not the access
point to environmental variables, but the `environ' global variable is,
so if someone feels like patching valgrind, they should watch `environ',
not the individual functions that modify it..)
--
sa...@ss... I have no opinions, since I cannot express any, after all.
If you think you saw an opinion, contact your optometrist.
|