https://bugs.kde.org/show_bug.cgi?id=411203
--- Comment #6 from Paul Floyd ---
It would probably be easiest to do this in valgrind itself. It already does
this to insert LD_PRELOADs for the core and tool vgpreaload libs.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=411203
Frank Ch. Eigler changed:
What|Removed |Added
CC||f...@redhat.com
--- Comment #5 from Frank
https://bugs.kde.org/show_bug.cgi?id=411203
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #4 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=411203
--- Comment #3 from Yann Droneaud ---
(In reply to Julian Seward from comment #2)
> (In reply to Yann Droneaud from comment #0)
>
> > Unfortunately, AFAICT, valgrind doesn't have (yet) support for altering the
> > tracee environment variables.
>
>
https://bugs.kde.org/show_bug.cgi?id=411203
--- Comment #2 from Julian Seward ---
(In reply to Yann Droneaud from comment #0)
> Unfortunately, AFAICT, valgrind doesn't have (yet) support for altering the
> tracee environment variables.
Why do you say that? AFAIK, V passes the env vars to the
https://bugs.kde.org/show_bug.cgi?id=411203
--- Comment #1 from Yann Droneaud ---
It shouldn't be difficult to implement, but it's a bit tricky as valgrind
launcher already communicate with each tool through environment variables.
So environment variable to be added/removed from tracee
