[PATCH] D12906: [RFC] Bug identification("issue_hash") change for CmpRuns.py

[Orbán György via cfe-commits]

Hi,

You are right the diff is is based on the hash. We already tried to
use an earlier hash generator (before the patch was introduced), which
generates a slightly different plist, that is why the current version
does not work with the patch.
We will fix CodeChecker to use new hash tag introduced in the final
patch (we did not change it so far because we didn't know what will be
the accepted naming convention and plist format).

We use LD_PRELOAD technique the log all the compiler calls, so no CC
or CXX environment variable orverride is necessary.
With the 'export CODECHECKER_VERBOSE=debug' enviromnet variable you
can see the analyzer commands.

Br,
Gyorgy


On Fri, Oct 23, 2015 at 2:25 PM, Honggyu Kim <hong.gyu.kim at lge.com> wrote:
> honggyu.kim added a comment.
>
> In http://reviews.llvm.org/D12906#273089, @xazax.hun wrote:
>
>> By default it is disabled for security reasons. You can enable by passing a command line option to the code checker, something like --not-host-only.
>
>
> Thanks, I can remotely access now with --not-host-only.
> But I cannot see the correct diff result when I click "Diff" button with two different Run Ids in List of runs menu.
> Is it working properly with your bug identification patch? (It has changed "issue_hash" field)
> Please correct me if I did something wrong.
>
> And here is one more question. I'm just wondering how CodeChecker runs clang static analyzer. Does it override CC and CXX just like scan-build?
> I can only see the actual build command with "-b" option as below:
>
>   CodeChecker check --dbusername test_user --dbport 5432 -n test_project_check -w ~/checker_workspace -b "cd my_test_project && make clean && make"
>
> Thank you!
>
>
> http://reviews.llvm.org/D12906
>
>
>