1. 25 Feb, 2016 1 commit
    • hjk's avatar
      Move analyzerbase to debugger · aaf05f5a
      hjk authored
      This is the first mechanical step to execute on the 'shared pool of
      debugger/analyzer views' idea.
      
      Future steps would be providing infrastructure for the view pool,
      making all analyzer/debugger views use the pool and then re-extract
      a sensible base for a 'analyzer-and/or-debugger' tool plugin interface.
      
      Change-Id: I1bb392e6dd3084fc56937956bee1d6fd9530335d
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      aaf05f5a
  2. 20 Jan, 2016 2 commits
  3. 25 Aug, 2015 1 commit
  4. 26 Jun, 2015 1 commit
  5. 27 Feb, 2015 1 commit
    • Christian Kandeler's avatar
      Allow users to suppress diagnostics. · 6e796591
      Christian Kandeler authored
      This patch deals with what is likely the most common use case:
      Filtering specific messages at a particular location. The current
      granularity is essentially per-file (and per-function, where possible),
      which seems more useful than taking line numbers into
      account, as that would not be robust with regards to code changes elsewhere
      in the file. We can fine-tune this if the need arises.
      
      Change-Id: I4e9b2671fa199339cc3b995953d072b840cd3205
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      6e796591
  6. 13 Feb, 2015 1 commit
  7. 12 Feb, 2015 1 commit
  8. 15 Jan, 2015 1 commit
  9. 25 Nov, 2014 1 commit
  10. 16 Oct, 2014 1 commit
    • Nikolai Kosjar's avatar
      Import Clang Static Analyzer plugin · b9f9eb7a
      Nikolai Kosjar authored
      This plugin adds "Clang Static Analyzer" to the Analyze mode, which
      processes all implementation/source project files of the current
      project. For this, it will call the clang executable for each file.
      
      The found diagnostics will be displayed in a view similar to the one
      used in "Valgrind Memory Analyzer".
      
      The user can specify the clang executable to use and the number of
      concurrent processes to launch in Menu: Tools > Options > Analyzer >
      Clang Static Analyzer.
      
      Main TODOs:
      
       * Fiddle around the appropriate command line options, currently only
         defines and include paths are passed on.
      
       * Tests on Windows / OS X.
      
       * Remove dependency to clangcodemodel by moving the functions that
         create command line arguments to CppTools. Mostly they are not even
         specific to clang (but would also work with gcc).
      
       * Maybe limit to a range of tested clang versions.
      
       * How to deal with directory containing all the log files after the
         user starts a new run or Creator is shut down? (delete it? leave it
         there? make it configurable?).
      
       * Find out how to properly integrate the tests.
      
      Imaginable future additions:
      
       * Adding a button to load result/log files from a directory, e.g. if
         the user used the 'scan-build' approach.
      
       * Adding a button with a filter menu in order to display only
         diagnostics from certain categories, similar to "Valgrind Memory
         Analyzer".
      
      Change-Id: I6aeb5dfdbdfa239a06c03dd8759a983df71b77ea
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>
      b9f9eb7a