1. 05 Apr, 2016 1 commit
  2. 07 Mar, 2016 1 commit
    • hjk's avatar
      Debugger: Merge debug mode and analyze mode · 92e301a0
      hjk authored
      On the user-visible side, only the 'Analyze' mode button disappears,
      and instead a combobox to switch between different tools in appears
      in the Debug mode toolbar.
      Internally, that's quite some re-organzition: The centralized
      'Analyze mode is busy' flag is gone, allowing us to run e.g.
      ClangStaticAnalyzer and MemCheck in parallel.
      Analyzer tools and debugger now share the same mechanism to
      generate/load/save dock widgets.
      Analyzer tools now create and handle their own start/stop button
      when appropriate. In general, Analyzer tools can create/handle more
      than one run control at a time.
      Further consolidation is possible, e.g. RunControl state handling
      could be merged into the base ProjectExplorer::RunControl to
      avoid the still existing duplication in ~15 instances.
      Change-Id: I91e5940ebc4211f98056d507cf2f7b5f8efe7f07
      Reviewed-by: default avatarChristian Stenger <christian.stenger@theqtcompany.com>
  3. 20 Jan, 2016 2 commits
  4. 25 Aug, 2015 1 commit
  5. 14 Jul, 2015 2 commits
  6. 26 Jun, 2015 1 commit
  7. 26 Feb, 2015 1 commit
  8. 30 Jan, 2015 1 commit
  9. 15 Jan, 2015 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
      Change-Id: I6aeb5dfdbdfa239a06c03dd8759a983df71b77ea
      Reviewed-by: default avatarEike Ziller <eike.ziller@theqtcompany.com>