1. 30 Aug, 2010 1 commit
  2. 27 Aug, 2010 1 commit
  3. 09 Aug, 2010 1 commit
  4. 20 Jul, 2010 1 commit
  5. 14 Jul, 2010 5 commits
  6. 08 Jul, 2010 2 commits
  7. 07 Jul, 2010 1 commit
  8. 30 Jun, 2010 1 commit
    • Friedemann Kleint's avatar
      Debugger[Trk]: Prepare thread handling. · 52b33a75
      Friedemann Kleint authored
      Store threads and cache registers per thread in Snapshot.
      As Trk does not generate Thread creation/deletion events.
      try to add threads on the fly if a stop in a new thread id is reported.
      Remove them in continue. Continue all threads in classic Trk.
      Pass on state (crash reason) to ThreadData and model.
      Factor out common code of both adapters to Snapshot/Symbian classes.
      52b33a75
  9. 29 Jun, 2010 1 commit
  10. 25 Jun, 2010 1 commit
    • Friedemann Kleint's avatar
      Debugger[Trk]: Added TCF experimental adapter. · beba423a
      Friedemann Kleint authored
      Added adapter to work with TCF over WLAN.
      Factor out common code for Symbian from TrkAdapter.
      Improve message logging in TrkGdbAdapter, some cleanup.
      Added new TcfTrkGdbAdapter based on TcfTrkDevice
      in symbianutils based on JSON, using QTcpSocket.
      To be started via special @tcf@ argument.
      Rubber-stamped-by: hjk
      beba423a
  11. 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
  12. 15 Jun, 2010 1 commit
  13. 14 Jun, 2010 2 commits
  14. 10 Jun, 2010 1 commit
  15. 18 May, 2010 1 commit
  16. 05 May, 2010 1 commit
  17. 09 Apr, 2010 1 commit
  18. 25 Mar, 2010 1 commit
  19. 18 Mar, 2010 1 commit
  20. 05 Mar, 2010 1 commit
  21. 01 Mar, 2010 1 commit
  22. 25 Feb, 2010 2 commits
  23. 11 Feb, 2010 7 commits
  24. 08 Feb, 2010 3 commits
  25. 05 Feb, 2010 1 commit