https://bugs.kde.org/show_bug.cgi?id=369209
--- Comment #7 from Mark Wielaard <m...@redhat.com> --- Created attachment 101309 --> https://bugs.kde.org/attachment.cgi?id=101309&action=edit new nocwd testcase How about this variant of the test. It tries a couple of things to make sure getcwd will fail. Create a path that is > PATH_MAX, make one component inaccessible and remove the current dir. Although all these things can be done on a linux system there is no error checking in case some different kernel doesn't allow any of these things. The testcase should fail (loop indefinitely) with current valgrind, but succeed with the patch. (You can check by running with ./vg-in-place -d --trace-children=yes none/test/nocwd and searching for "Getting the working directory at startup" - with the patch it will probably say "main ... <NO CWD>".) -- You are receiving this mail because: You are watching all bug changes.
