1. 17 Feb, 2011 1 commit
    • Friedemann Kleint's avatar
      Debugger: Reduce tooltip flicker. · c74da9b7
      Friedemann Kleint authored
      Move tooltip-request handling from DebuggerPlugin into
      DebuggerToolTipManager.
      
      Request tooltip only if position changed and close
      standard tooltip on success.
      c74da9b7
  2. 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
  3. 25 Jan, 2011 1 commit
  4. 12 Jan, 2011 2 commits
  5. 10 Jan, 2011 1 commit
  6. 17 Dec, 2010 2 commits
  7. 26 Nov, 2010 1 commit
  8. 16 Nov, 2010 1 commit
  9. 15 Nov, 2010 2 commits
    • Friedemann Kleint's avatar
      Debugger: Introduce BreakpointParameters as base struct. · 9fc5970b
      Friedemann Kleint authored
      For Breakpoint data manipulation.
      
      Reviewed-by: hjk
      9fc5970b
    • 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
  10. 29 Oct, 2010 1 commit
  11. 15 Oct, 2010 1 commit
  12. 23 Sep, 2010 1 commit
    • Friedemann Kleint's avatar
      Debugger: Fixes around watch editing. · 13c97d65
      Friedemann Kleint authored
      assignValueInDebugger: Pass on WatchData as well, pass
      on values as QVariant. Based on that, do more extensive
      checks in CDB, preventing assignment of non-PODs.
      
      Locals/Watch editing:
      * Disable while running
      * Edit pointer values as hex with validation.
      
      CDB: Strip class types off reported pointer values and reformat
      the values as short 0x-pointer values, introduce flag to
      WatchData::source to do dumper expansion handling.
      
      Windows: recognize int64 as int.
      
      Register handler: Fix accessing uninitialized value.
      13c97d65
  13. 21 Sep, 2010 1 commit
  14. 13 Sep, 2010 2 commits
  15. 01 Sep, 2010 1 commit
  16. 24 Aug, 2010 1 commit
    • Friedemann Kleint's avatar
      Debugger: Fix Symbian. · 54f9654b
      Friedemann Kleint authored
      ...which subclasses DebuggerRunner and does not call
      DebuggerPlugin::startDebugger(), which connects the
      engine, leading to strange malfunctions. Move functionality
      to DebuggerRunner::start() to make it self-contained.
      Add object names to engines for easier debugging.
      
      Reviewed-by: hjk
      54f9654b
  17. 23 Jul, 2010 1 commit
  18. 22 Jul, 2010 1 commit
  19. 14 Jul, 2010 5 commits
  20. 08 Jul, 2010 4 commits
  21. 07 Jul, 2010 2 commits
  22. 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
  23. 14 Jun, 2010 4 commits
  24. 04 May, 2010 1 commit
  25. 27 Apr, 2010 1 commit