Hi,
recently one very large file of ours cannot be analyzed any more, the analysis ends in a segfault. With 9f6a36c1a8a417838b04ceeb146b0bd2f0c0c1b0 it worked, with f2a419653cecc19e1c1a0cae6bb9016725e0f2a1 it doesn't.
My guess (!) is that is has something to do with this commit: https://github.com/danmar/cppcheck/commit/f2a419653cecc19e1c1a0cae6bb9016725e0f2a1 At least it is one that doesn't "just fix a FP". Also, there's a resulting segfault mentioned in the link above.
Does anyone else have a problem like this?
Thanks, Martin
I hope it will be fixed soonish. We also see crashes in our testing https://github.com/danmar/cppcheck/commit/f2a419653cecc19e1c1a0cae6bb9016725e0f2a1#commitcomment-66178530
Log in to post a comment.
Hi,
recently one very large file of ours cannot be analyzed any more, the analysis ends in a segfault.
With
9f6a36c1a8a417838b04ceeb146b0bd2f0c0c1b0
it worked, with
f2a419653cecc19e1c1a0cae6bb9016725e0f2a1
it doesn't.
My guess (!) is that is has something to do with this commit:
https://github.com/danmar/cppcheck/commit/f2a419653cecc19e1c1a0cae6bb9016725e0f2a1
At least it is one that doesn't "just fix a FP". Also, there's a resulting segfault mentioned in the link above.
Does anyone else have a problem like this?
Thanks,
Martin
I hope it will be fixed soonish. We also see crashes in our testing https://github.com/danmar/cppcheck/commit/f2a419653cecc19e1c1a0cae6bb9016725e0f2a1#commitcomment-66178530