1. 10 Jul, 2017 5 commits
  2. 07 Jul, 2017 5 commits
    • hjk's avatar
      Debugger: Connect GdbServerPortsGatherer signals in constructor · eb0aa0b7
      hjk authored
      Not in start(), when it would add extra connections on each re-run.
      
      Change-Id: I5fe9e047a188276f3bde54227dc0509ab77366c4
      Reviewed-by: Christian Kandeler's avatarChristian Kandeler <christian.kandeler@qt.io>
      eb0aa0b7
    • hjk's avatar
      Debugger: Use a SimpleTargetLaucher for gdbserver · 8f1f3330
      hjk authored
      Makes remote output appear again in the Application Output pane,
      and is arguably the right thing to do anyway.
      
      Change-Id: I05c365eec43f60a85482b8ae7d5856b3a31ee6f8
      Reviewed-by: Christian Kandeler's avatarChristian Kandeler <christian.kandeler@qt.io>
      8f1f3330
    • hjk's avatar
      ProjectExplorer: Remove RunControl::worker<Type>() · 8376afd9
      hjk authored
      It looks like the case where workers need talk to each other by
      only knowing the type of the 'partner' does not exist in practice
      anymore. With the now-common setup of a 'primary' worker that one
      can introduce the 'lesser' workers to each other directly.
      
      That's also conceptually more robust that picking a partner by
      type only only from some 'pool' (all the workers in a runcontrol),
      scales better (it e.g. is imaginable that a RunControl needs
      more than one PortGatherer in complex setups where more than one
      device is involved) saves a few cycles, and even removes the need
      for workers to be qobject_cast-able.
      
      Change-Id: Ib3d8c942c893d6c198d9813cce7df28ba3260ce8
      Reviewed-by: Christian Kandeler's avatarChristian Kandeler <christian.kandeler@qt.io>
      Reviewed-by: default avatarhjk <hjk@qt.io>
      8376afd9
    • hjk's avatar
      ProjectExplorer: Remove Connection as concept · f82bb1ec
      hjk authored
      It turns out that one "Connection" per RunControl doesn't map
      well to the uses we have. Instead, RunWorkers need to know
      individually how to connect to the place where they can work,
      but they are already specific enough to be able to use a
      standard class (like QUrl) as their way to specify the needed
      entry point.
      
      In theory one could see a RunControl's connection as an
      aggregation of its workers connection bits, but that does
      not really seem to be needed in code.
      
      As consequence, replace UrlConnection by a plain QUrl, and also
      the HostName connection by a QUrl with hostName set.
      
      Change-Id: I40c97e37779314ac0a77041e864a18eadb78f987
      Reviewed-by: Vikas Pachdha's avatarVikas Pachdha <vikas.pachdha@qt.io>
      f82bb1ec
    • Orgad Shaneh's avatar
      Debugger: Add missing state cases in quitDebugger · 72775ab8
      Orgad Shaneh authored
      * Aborting a core dump debugging is a valid state
      * Do not try to abort more than once (happens on shutdown)
      
      Change-Id: I075409b3fa1231420fcd72706b18eaa0383fd4f2
      Reviewed-by: default avatarhjk <hjk@qt.io>
      72775ab8
  3. 05 Jul, 2017 2 commits
  4. 04 Jul, 2017 1 commit
  5. 03 Jul, 2017 1 commit
  6. 30 Jun, 2017 1 commit
  7. 28 Jun, 2017 2 commits
  8. 27 Jun, 2017 1 commit
  9. 26 Jun, 2017 1 commit
  10. 23 Jun, 2017 3 commits
  11. 22 Jun, 2017 3 commits
  12. 21 Jun, 2017 1 commit
  13. 19 Jun, 2017 3 commits
  14. 16 Jun, 2017 1 commit
  15. 15 Jun, 2017 1 commit
  16. 12 Jun, 2017 1 commit
  17. 10 Jun, 2017 1 commit
  18. 02 Jun, 2017 2 commits
  19. 01 Jun, 2017 3 commits
  20. 30 May, 2017 1 commit
  21. 29 May, 2017 1 commit