1. 08 Jul, 2011 1 commit
  2. 06 Jul, 2011 1 commit
  3. 27 May, 2011 1 commit
  4. 06 May, 2011 1 commit
  5. 18 Apr, 2011 1 commit
  6. 13 Apr, 2011 1 commit
  7. 12 Apr, 2011 2 commits
    • Friedemann Kleint's avatar
      Debugger: Have Python dumper print type size information. · 67d39101
      Friedemann Kleint authored
      For memory views. In the dumper, create a cache of TypeInfo
      structs to contain type information and print the new entries
      in each call of bb().
      
      Collect the information in the gdb engine.
      Replace WatchData::origAddress by WatchData::ReferencingAddress
      to be able to correctly handle automatically dereferenced
      pointers of the gdb engine. Whereas 'address' of a automatically
      dereferenced used to be that of the pointer, it is now that
      of the dereferenced item matching the size reported, enabling
      memory views. Referencing address is now the address of the pointer.
      
      Reviewed-by: hjk
      67d39101
    • hjk's avatar
      e7441dab
  8. 25 Feb, 2011 1 commit
  9. 11 Feb, 2011 1 commit
    • Friedemann Kleint's avatar
      Debugger: Make tooltips pinnable. · 0ac879e3
      Friedemann Kleint authored
      Replace old debugger tooltip by a new ToolTipManager which
      has a list of AbstractDebuggerToolTipWidget with the functionality
      to 'acquire' an engine (display its data) and 'release' it
      (store engine data and display them as 'previous') and serialization
      to XML session data.
      DebuggerTreeViewToolTipWidget implements AbstractDebuggerToolTipWidget
      for tree model acting as  a filter on watch models.
      
      Rubber-stamped-by: hjk
      0ac879e3
  10. 08 Feb, 2011 1 commit
  11. 12 Jan, 2011 2 commits
  12. 10 Jan, 2011 1 commit
  13. 17 Dec, 2010 1 commit
  14. 29 Nov, 2010 1 commit
  15. 15 Nov, 2010 1 commit
    • hjk's avatar
      debugger: Refactor breakpoint handling. · 8ae541b3
      hjk authored
      The breakpoints are now (fairly) tightly guarded by the BreakpointHandler.
      Engines and Views are only supposed to refer to them by id. They also have
      individual states now. The breakpoint data is split into a "user requested"
      "fixed" part in BreakpointData and the engines' acknowledged data in a new
      struct BreakpointResponse.
      
      TODO: Move m_state and m_engine members to BreakpointResponse. Fix regressions
      in the marker handling.
      8ae541b3
  16. 10 Nov, 2010 1 commit
  17. 04 Nov, 2010 1 commit
  18. 02 Nov, 2010 1 commit
  19. 08 Oct, 2010 1 commit
  20. 28 Sep, 2010 1 commit
  21. 23 Sep, 2010 1 commit
  22. 22 Sep, 2010 1 commit
  23. 10 Sep, 2010 1 commit
    • Friedemann Kleint's avatar
      I10N: First translation fixes for 2.1 · 24cadd34
      Friedemann Kleint authored
      Fix README, some spelling errors, remove contractions,
      exclamation marks, correct some plural forms, join split messages.
      Add QCoreApplication::translate to non-Q_OBJECT-classes.
      Fix some lupdate warnings about discarding meta-data (//:).
      24cadd34
  24. 08 Sep, 2010 2 commits
  25. 01 Sep, 2010 2 commits
  26. 27 Aug, 2010 1 commit
  27. 21 Jul, 2010 2 commits
  28. 14 Jul, 2010 2 commits
  29. 22 Jun, 2010 1 commit
    • hjk's avatar
      debugger: The DebuggerEngine refactoring. · 6a6cba55
      hjk authored
      This replaces the (de facto) singleton engines and data handlers by classes
      that are instantiated per run. The DebuggerRunControl will now create an
      object of (a class derived from) DebuggerEngine that contains all the relevant
      "dynamic" data.
      
      DebuggerManager is no more. The "singleton" bits are merged into DebuggerPlugin,
      whereas the data bits went to DebuggerEngine.
      
      There is no formal notion of a "current" DebuggerEngine. However, as there's
      only one DebuggerEngine at a time that has its data models connected to the
      view, there's still some "de facto" notion of a "current" engine. Calling
      SomeModel::setData(int role, QVariant data) with custom role is used as the
      primary dispatch mechanism from the views to the "current" data models
      (and the engine, as all data models know their engine).
      6a6cba55
  30. 14 Jun, 2010 3 commits
  31. 11 Jun, 2010 1 commit
  32. 10 Jun, 2010 1 commit