1. 05 Apr, 2016 1 commit
  2. 10 Mar, 2016 1 commit
  3. 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>
  4. 02 Mar, 2016 2 commits
  5. 29 Feb, 2016 1 commit
  6. 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>
  7. 22 Jan, 2016 1 commit
  8. 20 Jan, 2016 3 commits
  9. 07 Jan, 2016 1 commit
  10. 25 Nov, 2015 1 commit
  11. 13 Nov, 2015 1 commit
  12. 25 Aug, 2015 1 commit
  13. 01 Jul, 2015 1 commit
  14. 30 Jun, 2015 1 commit
  15. 26 Jun, 2015 1 commit
  16. 05 May, 2015 1 commit
  17. 27 Apr, 2015 1 commit
  18. 09 Mar, 2015 2 commits
    • Christian Kandeler's avatar
      Create a dummy run configuration to create our run control from. · 10acf6af
      Christian Kandeler authored
      The Clang Static Analyzer differs from other analyzers in that it does
      not run a binary produced by the build process, but looks at source
      files instead. It is therefore completely unrelated to any run
      configurations that may or may not exist for the project. This has been
      ignored so far, with these two main consequences:
          - When running the analyzer, the name of some random run
            configuration appears in the application output pane, which makes
            it look to the user as if the corresponding executable has been
            run, which it has not.
          - For projects without run configurations (e.g. libraries),
            analyzing does not work out of the box, which makes no sense
      So we now create our own run special run configuration (not visible in
      the UI) and run it directly via runRunConfiguration() instead of using
      the currently active run configuration via runProject().
      This fixes both issues listed above.
      Change-Id: Icc839816f4a1e6f02a0eb2328c536b44f7304807
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
    • Christian Kandeler's avatar
      Show the status message also while running. · 26abab90
      Christian Kandeler authored
      So users can see how many issues were found before the analyzer has
      finished, as well as browse them.
      Change-Id: I82452441168ecb370e7b2aac137961ebb5b8bfc3
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
  19. 27 Feb, 2015 2 commits
  20. 26 Feb, 2015 1 commit
  21. 20 Feb, 2015 1 commit
  22. 19 Feb, 2015 1 commit
  23. 09 Feb, 2015 1 commit
    • Christian Kandeler's avatar
      Add unit tests. · 2946364c
      Christian Kandeler authored
      These test the complete workflow as the user experiences it when
      clicking "Start".
      Intended usage:
          (1) Run sdktool to set up a kit with the toolchain you want
              to test against (using a temporary directory).
              The tests assume exactly one Kit to be present.
          (2) Start Creator with a matching settings path and
              "-load ClangStaticAnalyzer -test ClangStaticAnalyzer".
          (3) Repeat until all toolchains have been tested.
      The initial implementation tests one trivial source file
      with both qbs and qmake.
      Change-Id: I810f23e2990a789a4dd9f1dd16335fbcf5c5f39f
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
  24. 15 Jan, 2015 1 commit
  25. 25 Nov, 2014 1 commit
  26. 24 Nov, 2014 1 commit
  27. 07 Nov, 2014 2 commits
  28. 31 Oct, 2014 2 commits
  29. 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>