Daniel Marjamäki

I reopen this issue because people still have problems we'll need to solve it properly.

thanks for clarifying this message it's needed. :+1: > Maybe we can just reword the message by including the term "unnecessary copy" which would also be closer to the performance-unnecessary-value-param...

> Possible solutions: Maybe we can reword that somehow so it indicates that it's not a exhaustive list of all possible solutions. But only some suggestions how it can be...

Two questions: * you CAN install cppcheck binary and all the datafiles in a installation folder.. I wonder if you don't install cppcheck in some standard /usr/bin etc folder anyway...

> We install in something like /cvmfs/sft.cern.ch/lcg/releases/cppcheck//

> A case against supporting CWD in the lookup (from https://github.com/danmar/cppcheck/pull/7639#discussion_r2192049596): Maybe I missed it? I do not see an alternative suggestion yet how configuration files would be found in...

> "It will look in the folder you run Cppcheck from. So on Linux, if you have files in your user folder (like we support in the GUI). And you...

> But you just gave the use case for CWD. If you have a custom script which invokes it you might place addition or overrides next to the script. The...

Well an option could be added to specify this path. However my feeling is that there are many users that have been putting custom platform files or configuration files in...

> Since we execute Python code I wonder if we restrict that execution out-of-the-box (e.g. restrict process permissions, sandboxing, ...) so the code we run cannot do any obviously malicious...