[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Aron Budea changed: What|Removed |Added Blocks||143781 Referenced Bugs:

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Buovjaga changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #43 from Buovjaga --- (In reply to adityapratapsingh51 from comment #42) > So, does this EasyHack involve uploading updated tarfile of scan-build > report or does it involve solving the bug reports in the scan-build report?

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #42 from adityapratapsing...@gmail.com --- So, does this EasyHack involve uploading updated tarfile of scan-build report or does it involve solving the bug reports in the scan-build report? -- You are receiving this mail

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #41 from Buovjaga --- (In reply to adityapratapsingh51 from comment #40) > Has all work in this hack been completed? > If not, can someone please provide me with a list of what all is yet to be > done? Read the

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #40 from adityapratapsing...@gmail.com --- Has all work in this hack been completed? If not, can someone please provide me with a list of what all is yet to be done? -- You are receiving this mail because: You are the

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #39 from Maarten Hoes --- A first version of a shell script that can automate the generation of the reports has been put up for review in gerrit: https://gerrit.libreoffice.org/c/dev-tools/+/104372 -- You are receiving this

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #38 from Maarten Hoes --- Created attachment 166253 --> https://bugs.documentfoundation.org/attachment.cgi?id=166253=edit Full scan-build report of the LibreOffice codebase. This attachment is a compressed tarfile,

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #37 from Maarten Hoes --- Well, I finally got around to testing this, and the '--exclude' option seems to work as expected. If you run 'scan-build' with (among others) these options : --exclude $src/*/UnpackedTarball/*

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #36 from Maarten Hoes --- I just noticed this option in the output of clang9 'scanbuild -h' : --exclude Do not run static analyzer against files found in this directory (You can specify this option multiple times).

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Buovjaga changed: What|Removed |Added Assignee|dmou...@cs.iitr.ac.in |libreoffice-b...@lists.free

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Diya Mourya changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |dmou...@cs.iitr.ac.in

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Diya Mourya changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #34 from Diya

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #33 from Maarten Hoes --- One of the problems with doing this, as far as I can see, is this: The developers of LibreOffice seem to be interested only/primarily in analyzing the core LibreOffice

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #32 from Fakabbir amin --- I am still trying to figure out, how to get it done without errors. Until then I am setting it to unassigned. -- You are receiving this mail because: You are the assignee for

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Fakabbir amin changed: What|Removed |Added Status|ASSIGNED|NEW

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Fakabbir amin changed: What|Removed |Added Assignee|libreoffice-b...@lists.free

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 jan iversen changed: What|Removed |Added Whiteboard|ToBeReviewed| --

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 jan iversen changed: What|Removed |Added Whiteboard|target:4.5.0

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #28 from danichocolate...@gmail.com --- Hi, Yes you are right. My bad -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #24 from Maarten Hoes hoes.maar...@gmail.com --- (In reply to danichocolate714 from comment #23) I am building this as https://wiki.documentfoundation.org/Development/Clang_Code_Analysis described now... But I am not sure

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #25 from danichocolate...@gmail.com --- Hi Maarten, 1 I finished the build and checked all the comments to this issue again. Then did I realize as Julien Nabet mentioned: there are reports produced every one or two weeks (By

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #26 from Julien Nabet serval2...@yahoo.fr --- (In reply to danichocolate714 from comment #25) Hi Maarten, 1 I finished the build and checked all the comments to this issue again. Then did I realize as Julien Nabet

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #27 from Maarten Hoes hoes.maar...@gmail.com --- Hi, I think you are confusing two different kinds of reports here. You mention the cppcheck reports located at : http://dev-builds.libreoffice.org/cppcheck_reports/master/

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 --- Comment #23 from danichocolate...@gmail.com --- I am building this as https://wiki.documentfoundation.org/Development/Clang_Code_Analysis described now... But I am not sure what should I look for. To see if clang can find any bugs? Can

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Maarten Hoes hoes.maar...@gmail.com changed: What|Removed |Added See Also|https://bugs.freedesktop.or |

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Maarten Hoes hoes.maar...@gmail.com changed: What|Removed |Added CC|hoes.maar...@gmail.com |

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Maarten Hoes hoes.maar...@gmail.com changed: What|Removed |Added URL|https://wiki.documentfounda

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.documentfoundation.org/show_bug.cgi?id=39596 Maarten Hoes hoes.maar...@gmail.com changed: What|Removed |Added CC|

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #21 from Commit Notification libreoffice-comm...@lists.freedesktop.org --- Juan Picca committed a patch related to this issue. It has been pushed to master:

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 Commit Notification libreoffice-comm...@lists.freedesktop.org changed: What|Removed |Added Whiteboard|EasyHack

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #18 from Thomas Arnhold tho...@arnhold.org --- Is it possible to update the folders automatically on a weekly basis? The same could apply to cppcheck stuff. I think this is a good entry point for new contributers. -- You are

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 Julien Nabet serval2...@yahoo.fr changed: What|Removed |Added See Also|

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 Björn Michaelsen bjoern.michael...@canonical.com changed: What|Removed |Added CC|

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 John Smith lbalba...@gmail.com changed: What|Removed |Added URL|http://dev-builds.libreoffi

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 John Smith lbalba...@gmail.com changed: What|Removed |Added URL|

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #16 from John Smith lbalba...@gmail.com 2012-08-21 17:00:26 UTC --- The new, permanent home for the clang analyzer reports is : http://dev-builds.libreoffice.org/clang_reports/ -- Configure bugmail:

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #15 from John Smith lbalba...@gmail.com 2012-08-18 10:16:35 UTC --- I have run the analyzer on master (2012-08-15), but now with the clang compiler instead of using gcc for compilation (in order to prevent this error error: use of

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #14 from John Smith lbalba...@gmail.com 2012-08-04 10:24:04 UTC --- Please do note that the C++ *analyzer* (not the compiler) is still very much regarded as a 'work-in-progress' at this point in time (2012-08-01), so you are likely

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #13 from John Smith lbalba...@gmail.com 2012-08-03 07:09:55 UTC --- I have run the clang analyzer on LibreOffice master ~2012-08-02 with '--with-system-libs' in order to exclude reporting of issues in 3rd party code. The only

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 --- Comment #12 from John Smith lbalba...@gmail.com 2012-07-29 20:23:06 UTC --- I have run and uploaded a full html report of LibreOffice master ~2012-07-28 at : http://lbalbalba.x90x.net/clang-analyzer/libreoffice/ for the time being. If

[Libreoffice-bugs] [Bug 39596] use the CLang++ static analyser to find bugs

https://bugs.freedesktop.org/show_bug.cgi?id=39596 Florian Reisinger reisi...@gmail.com changed: What|Removed |Added Summary|[EasyHack] use the CLang++ |use the CLang++