xazax.hun added a comment.
You might want to give CodeChecker [1] a try as a workaround. It stores the
results in a more compact format and you can do filtering.
[1] https://github.com/Ericsson/codechecker
https://reviews.llvm.org/D28765
___
cfe-c
vlad.tsyrklevich abandoned this revision.
vlad.tsyrklevich added a comment.
The motivation was to make resulting output easier to navigate and to cut the
result size by ~90%, one default run against the FreeBSD kernel takes 3 gigs of
storage and I'm running several builds a day as I iterate on c
zaks.anna added a comment.
> It is not supported to run the analyzer with some of the core checkers turned
> off.
Correct.
> Maybe we should change the behavior such that turning off core checkers turn
> off the warnings from those checkers but not the checkers themselves?
Having this as the
xazax.hun added a comment.
It is not supported to run the analyzer with some of the core checkers turned
off. Maybe we should change the behavior such that turning off core checkers
turn off the warnings from those checkers but not the checkers themselves?
https://reviews.llvm.org/D28765
__
vlad.tsyrklevich created this revision.
vlad.tsyrklevich added reviewers: cfe-commits, zaks.anna, dcoughlin, NoQ.
CStringChecker assumes that SVals are not undefined at two points with comments
stating that other checkers will check for that condition first; however, it
can crash if a user choos
