1. 22 Jun, 2014 1 commit
  2. 12 Jun, 2014 1 commit
  3. 06 Jun, 2014 1 commit
  4. 21 May, 2014 1 commit
    • Lasse Liehu's avatar
      Fix session name display in session runner · bd20450e
      Lasse Liehu authored
      Session name was shown twice because SessionPrettyContents
      already contains it. This caused the runner to display names like:
      "kdevelop: kdevelop: kdevelop, kdevplatform"
      where kdevelop was the session name and kdevelop and kdevplatform
      were the projects open in that session.
      
      REVIEW: 118185
      bd20450e
  5. 04 May, 2014 1 commit
  6. 02 May, 2014 2 commits
  7. 29 Apr, 2014 1 commit
  8. 02 Apr, 2014 2 commits
  9. 01 Apr, 2014 1 commit
  10. 20 Mar, 2014 1 commit
  11. 19 Mar, 2014 1 commit
  12. 14 Feb, 2014 1 commit
  13. 13 Feb, 2014 1 commit
    • Kevin Funk's avatar
      GDB: Handle missing 'original-location' gracefully · 5625aa7e
      Kevin Funk authored
      Tested with GDB as of version 7.7 (released in 2014, Jan).
      We may not have the 'original-location' field in all cases.
      This happened when "catch throw" was used in gdbinit.
      
      TODO: Check what we can do in case we don't get a source location at
      all. Currently we might end up having empty lines in the breakpoint
      table.
      
      @Vlas, please review
      5625aa7e
  14. 10 Feb, 2014 2 commits
  15. 09 Feb, 2014 1 commit
  16. 06 Feb, 2014 1 commit
    • Oleksandr Senkovych's avatar
      Fix inspecting of nested STL containers. · 8da1e659
      Oleksandr Senkovych authored
      The problem is that GDB MI shows no children for dynamic STL objects,
      it just add "dynamic" attribute to it. Here is -var-list-children
      output for std::map< int, std::vector<std::string> > object:
      
      SEND: "-var-list-children --thread 1 --frame 0 --all-values "var1" 0 5
      kdevelop(20230)/kdevelop (gdb debugger) GDBDebugger::GDB::processLine:
      GDB output:
      "^done,numchild="2",displayhint="map",children=[child={name="var1.[0]",
      exp="[0]",numchild="0",value="0",type="const int",thread-id="1"},
      child={name="var1.[1]",exp="[1]",numchild="0",value="{...}",
      type="std::vector<std::basic_string<char, std::char_traits<char>,
       std::allocator<char> >, std::allocator<std::basic_string<char,
      std::char_traits<char>, std::allocator<char> >
      > >",thread-id="1",displayhint="array",dynamic="1"}],has_more="0""
      
      As you see, the second variable, std::vector<std::string> has
      numchild="0", but dynamic="1". This patch adds extra check for
      "dynamic" attribute in variables.
      
      BUG: 330734
      (cherry picked from commit 751488d0)
      8da1e659
  17. 19 Jan, 2014 1 commit
  18. 02 Jan, 2014 1 commit
  19. 30 Dec, 2013 1 commit
  20. 28 Dec, 2013 9 commits
  21. 23 Dec, 2013 1 commit
  22. 16 Dec, 2013 1 commit
    • Milian Wolff's avatar
      Don't crash when the CMakeLists.txt structure contains 'gaps'. · b86a12d2
      Milian Wolff authored
      With gaps, I mean folder structures such as this:
      
      /CMakeLists.txt -> add_subdirectory(foo/bar)
      /foo -> (no CMakeLists.txt)
      /foo/bar/CMakeLists.txt
      
      In this case, when we edited the last CMakeLists.txt, KDevelop would
      crash as it cannot find a context for the direct parent folder.
      Instead, we now recurse until we hit the project root. If no context
      can be found, we fallback to initialize the project with the current
      folder.
      
      Note: This could be reproduced 100% of the cases when editing a
      CMakeLists.txt in one of the sub folders of kdevplatform/language.
      
      BUG: 327120
      b86a12d2
  23. 15 Dec, 2013 1 commit
    • Milian Wolff's avatar
      Do not duplicate namespace-local declarations in code-completion. · 691205fc
      Milian Wolff authored
      When a namespace context gets reopened, we also look into its
      previous declarations. But if those contexts are (going to) be handled
      as well, we ended up adding their local declarations multiple times
      into the completion list.
      
      This is now fixed by tracking which contexts we (will) look into.
      
      BUG: 328803
      691205fc
  24. 12 Dec, 2013 5 commits
  25. 11 Dec, 2013 1 commit