Re: llvm/clang static analyzer reports

On 01/10/2020 08:59, Stephan Bergmann wrote: * For example, "Use-after-free" 2020-09-30-155842-506845-1/report-366f11.html#EndPath (presumably along with many, many other of the 827 Use-after-free) is clearly a false positive:  While VclPtr::disposeAndClear holds   ::rtl::Reference aTmp(m_rI

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 15, 2020 at 6:51 PM Stephan Bergmann wrote: > On 15/10/2020 10:58, Stephan Bergmann wrote: > > On 15/10/2020 09:51, Maarten Hoes wrote: > >> Just one more thing I need to mention. At some point during the > >> build/analysis, I run into the following: > >> > >> The analyzer (or

Re: llvm/clang static analyzer reports

On 15/10/2020 10:58, Stephan Bergmann wrote: On 15/10/2020 09:51, Maarten Hoes wrote: Just one more thing I need to mention. At some point during the build/analysis, I run into the following: The analyzer (or make, I can't tell which) goes looking for '/usr/bin/clang-10++' (which isn't there)

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 15, 2020 at 10:58 AM Stephan Bergmann wrote: > > We can have a look once you have sent something to Gerrit. > > Ok. I put it up for review: https://gerrit.libreoffice.org/c/dev-tools/+/104372 As requested, I added you as a reviewer. - Maarten _

Re: llvm/clang static analyzer reports

On 15/10/2020 09:51, Maarten Hoes wrote: Just one more thing I need to mention. At some point during the build/analysis, I run into the following: The analyzer (or make, I can't tell which) goes looking for '/usr/bin/clang-10++' (which isn't there) instead of '/usr/bin/clang++-10'. In other w

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 15, 2020 at 8:48 AM Stephan Bergmann wrote: > Sure, can't hurt to document the approach you've taken. So if that's > not much additional work, sounds good to me to add a script to > dev-tools. You can add me as reviewer. Alright, I'll do that then. Just one more thing I nee

Re: llvm/clang static analyzer reports

On 14/10/2020 20:08, Maarten Hoes wrote: If there is enough interest, I can create a shell script that automates the procedure of running the clang static analyzer on the LibreOffice codebase, so that it can be run on a regular basis in an automated fashion. If so, I would like to submit that s

Re: llvm/clang static analyzer reports

Hi, If there is enough interest, I can create a shell script that automates the procedure of running the clang static analyzer on the LibreOffice codebase, so that it can be run on a regular basis in an automated fashion. If so, I would like to submit that script to gerrit, so that it can be revi

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 1, 2020 at 8:59 AM Stephan Bergmann wrote: We would need some mechanism to filter > out such identified false positives, with whatever mechanism would be > suitable: an annotation in the source code, a modification of the > -analyzer-... command line options passed to clang, etc.

Re: llvm/clang static analyzer reports

On 30/09/2020 21:36, Maarten Hoes wrote: [2] https://drive.google.com/file/d/1kbX_uo_jRqQkny1Qf6XYT1d72nUC8PO0/view?usp=sharing The last discussion I find about running Clang Static Analyzer on the LibreOffice code base is the mail thread