https://bugs.kde.org/show_bug.cgi?id=513403
--- Comment #3 from nickb <[email protected]> --- I don't insist on my interpretation being correct, but I find it dubious that this behavior is (a) not clearly documented and (b) depends on the code executed in the child process. When I invoke a cli-application I expect the application to treat any path I supplied as relative to the `cwd` of the environment the application was called in. I imagine this behavior is a consequence of the way valgrind is implemented, but I think it shouldn't be too hard to convert any relative path into an absolute one before continuing execution. That being said, I can imagine this kind of behavior being useful for the case when each executable has a `.supp` file in its `cwd` and we want to dynamically use those as we chain call through those. But it seems like a very special case and given this behavior isn't documented, I doubt anyone ever realized this was an option, let alone use it in any real context. That being said, I'm not opposed to the idea of implementing the fix I've outlined above or documenting the current behavior if anyone is willing to review the fix/doc patch. Let me know. -- You are receiving this mail because: You are watching all bug changes.
