[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #9 from Mark Wielaard --- (In reply to Ivo Raisr from comment #8) > the new test case works ok (I am able to simulate the problem on Solaris) > with 'make one component inaccessible'. Thanks for testing. Lets go with this

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #8 from Ivo Raisr --- Hi Mark, the new test case works ok (I am able to simulate the problem on Solaris) with 'make one component inaccessible'. Please include "string[s].h" for proper strlen declaration. My apologies it

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #7 from Mark Wielaard --- Created attachment 101309 --> https://bugs.kde.org/attachment.cgi?id=101309=edit new nocwd testcase How about this variant of the test. It tries a couple of things to make sure getcwd will fail.

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #6 from Ivo Raisr --- Yes, cwd of another process can be removed; but as usually the process holds a reference on it: "If the directory's link count becomes zero and no process has the directory open,

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #5 from Mark Wielaard --- (In reply to Ivo Raisr from comment #4) > So this simple change fixes the warning: > - execlp ("echo", "echo", "Hello", "World", NULL); > + execlp ("echo", "echo", "Hello", "World", (char *)

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #4 from Ivo Raisr --- Hi Mark, I get this compilation warning on Solaris: nocwd.c: In function ‘main’: nocwd.c:28:3: warning: missing sentinel in function call [-Wformat=] execlp ("echo", "echo", "Hello", "World",

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #3 from Ivo Raisr --- Will do. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 Mark Wielaard changed: What|Removed |Added CC||iv...@ivosh.net,

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #1 from Mark Wielaard --- Created attachment 101237 --> https://bugs.kde.org/attachment.cgi?id=101237=edit Don't require the current working directory to exist. At startup valgrind fetches the current working directory