1. 10 Jan, 2011 1 commit
  2. 20 Dec, 2010 1 commit
  3. 17 Dec, 2010 1 commit
  4. 17 Nov, 2010 1 commit
    • Oswald Buddenhagen's avatar
      overhaul process argument handling · 1e362b0f
      Oswald Buddenhagen authored
      get away from argument stringlists. instead, use native shell command
      lines which support quoting/splitting, environment variable expansion
      and redirections with well-understood semantics.
      
      Task-number: QTCREATORBUG-542
      Task-number: QTCREATORBUG-1564
      1e362b0f
  5. 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
  6. 21 Jul, 2010 1 commit
  7. 14 Jul, 2010 3 commits
  8. 08 Jul, 2010 2 commits
  9. 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
  10. 15 Jun, 2010 1 commit
  11. 14 Jun, 2010 1 commit
  12. 19 May, 2010 1 commit
  13. 12 May, 2010 1 commit
  14. 05 May, 2010 1 commit