Add a mode where CTU files are retained

[tomrittervg]

For debugging purposes I wanted to retain the CTU files. In case this sounds useful, I'll throw the patch here.

[bruntib]

Hi,

Thanks for the patch! However, as a rule of thumb, we would like to go in the direction of not introducing further flags unless it's unavoidable otherwise.

CodeChecker analyze command has --ctu-collect and --ctu-analyze flags. The first one is producing the CTU files and the second one is using them for analysis. The --ctu flag is almost equivalent with providing both flags. When we need to debug the generated CTU files, then we run --ctu-collect only. Would you think, this is a good methodology for testing CTU?

[tomrittervg]

Personally that won't work for me because I need to run the entire thing overnight, --ctu-analyze will delete the files when its done, and my ctu-dir is >400GB so I don't want to copy the files just to move them back after they're deleted; but I understand it's a fringe case so I'm not upset if you don't want to take the patch.

[bruntib]

I understand the motivation and I agree with having a solution for debugging reasons. I'm just suggesting an alternative solution to execute the analysis in two phases. I mean if you execute CodeChecker analyze with --ctu-collect and --ctu-analyze separately, then the analysis is the same and ctu-dir is not removed.

[tomrittervg]

I understand the motivation and I agree with having a solution for debugging reasons. I'm just suggesting an alternative solution to execute the analysis in two phases. I mean if you execute CodeChecker analyze with --ctu-collect and --ctu-analyze separately, then the analysis is the same and ctu-dir is not removed.

Oh, I misunderstood or mis-remembered the code then, I thought it was still removed after ctu-analyze even if it was two phases, but that doesn't seem to be the case.

Thanks, I will migrate to that pattern at some point.