|
From: Nicholas N. <nj...@ca...> - 2003-08-14 07:50:19
|
On Thu, 14 Aug 2003, Santeri Paavolainen wrote: > >Or simpler, just wrapper setenv and putenv and force valgrind's paths > >in and prevent VG_ARGS from being changed, but I worry slightly that an > >app might assume it knows how long a variable is because it just set it > >- something like this rather stupid contrived example: > > > To this work, you need to also monitor accesses to the `environ' global > variable. Perhaps that is actually easier, since `putenv', `clearenv' > etc. manipulate just that single global variable. 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? N |