Review Request 129768: Fix segfault when analyzing source code with clang-tidy

[Leslie Zhai]

> On Jan. 5, 2017, 5:59 p.m., Kevin Funk wrote:
> > I think that's the wrong solution, we should still be able to run clang-tidy, even without a BSM.
> > 
> > Did you try just skipping setting the build directory if there's no BSM?

Hmmm, manually reproduced the issue is *NOT* easy! perhaps we can use Clang Static Analyzer to scan-build kdev-clang-tidy to find potentional issues ;-)


- Leslie


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129768/#review101818
-----------------------------------------------------------


On Jan. 5, 2017, 11:55 a.m., Leslie Zhai wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/129768/
> -----------------------------------------------------------
> 
> (Updated Jan. 5, 2017, 11:55 a.m.)
> 
> 
> Review request for KDevelop and Kevin Funk.
> 
> 
> Bugs: 374525
>     https://bugs.kde.org/show_bug.cgi?id=374525
> 
> 
> Repository: kdev-clang-tidy
> 
> 
> Description
> -------
> 
> Hi KDevelop developers,
> 
> KDevelop segfault when analyzing source code with clang-tidy, so I simply added ```if (!buildSystem)``` check
> 
> Regards,
> Leslie Zhai
> 
> 
> Diffs
> -----
> 
>   src/plugin.cpp 0def66e 
> 
> Diff: https://git.reviewboard.kde.org/r/129768/diff/
> 
> 
> Testing
> -------
> 
> Analyzed K3B with clang-tidy
> 
> 
> Thanks,
> 
> Leslie Zhai
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170106/daf18df5/attachment.html>