1. 28 Aug, 2017 1 commit
  2. 02 Aug, 2017 2 commits
  3. 01 Aug, 2017 1 commit
  4. 30 Mar, 2016 1 commit
  5. 19 Jan, 2016 1 commit
  6. 03 Jun, 2015 1 commit
  7. 06 Jan, 2015 1 commit
    • Denis Shienkov's avatar
      BareMetal: Allow to manage configurations of HW GDB servers · 165f008d
      Denis Shienkov authored
      The user has only one possibility to setup of the remote GDB server
      when a new device is created (or to modify it for existing device).
      It is possible only in the host/port fields for connection to the
      GDB server. It is a little inconvenient for the user. If the user
      wants to use other configuration of the GDB server, then need every
      time to edit the current configuration.
      
      Improving this it is introduction a new concept with a new entity
      named as "GDB server provider". Now to the device debugging purpose
      the user can choose any of the GDB provider from the list (by analogy
      with toolchain and so on). Each configuration of GDB provider is
      created by the user manually on the new "GDB Server Provider" options
      page. This can be made before or after creation of device.
      
      A GDB server provider can work in three startup modes (depends on
      implementation of concrete provider):
      
      1) NoStartup mode.
      
      This means that we do not want to startup a provider, we just trying
      to connect to the already started GDB provider server. This mode uses
      the TCP/IP connection with manually specifying of remote host and port.
      
      2) StartupOnNetwork mode.
      
      This means that we want to launch of the GDB provider automatically
      before connect to it in process of remote debugging. This mode also
      uses the TCP/IP protocol. In addition to it, a GDB provider can has
      additional options which are contains a paths to provider executable
      file, to configuration files and so on (it is depends on concrete
      provider implementation). This mode (with NoStartup) covers about 90%
      of usecase, and is supported by most set of the GDB server providers.
      
      3) StartupOnPipe mode.
      
      This is similar to StartupOnNetwork mode and we also automatically
      starts the GDB server provider before debugging. But in this case is
      used the Pipe mode instead of TCP/IP. Not each of the GDB provider
      can support debugging via pipes.
      
      This patch has concrete implementations for a following set of the
      GDB server providers:
      
      * "Default" provider which supports only the NoStartup mode.
      
      * "Open On-Chip Debugger" (http://openocd.sourceforge.net/)
        provider which supports all modes.
      
      * "STLinkUtil" (https://github.com/texane/stlink)
        provider which supports NoStartup and StartupOnNetwork modes.
      
      Tested on Windows and Linux with:
      
      * target HW: ARM Stm32F4Discovery board with HW debugger STLink-v2
      * provider: OpenOCD v0.8.0 (tested on Windows and Linux)
      * provider: STLink-Util (tested on Linux only)
      * toolchain: ARM GCC v4.9.2
      * debugger: GDB v7.8.1 (with Python support)
      * QtCreator with QBS project
      
      Task-number: QTCREATORBUG-13686
      Change-Id: I59c775d91b0a4227d931188879850c536290e1ba
      Reviewed-by: default avatarLeena Miettinen <riitta-leena.miettinen@theqtcompany.com>
      Reviewed-by: default avatarhjk <hjk@theqtcompany.com>
      165f008d
  8. 09 Oct, 2014 1 commit
  9. 08 Jan, 2014 1 commit
  10. 03 Oct, 2013 1 commit
  11. 13 Sep, 2013 1 commit
  12. 29 Jan, 2013 1 commit
  13. 05 Oct, 2012 1 commit
  14. 05 Sep, 2012 1 commit
    • Friedemann Kleint's avatar
      KitChooser: Introduce virtual methods for Debugger. · c3f50e31
      Friedemann Kleint authored
      Introduce virtual methods such that it is possible to
      write derived classes for specific KitInformation classes,
      allowing for filtering and setting text and tooltip.
      
      Remove debugging-specific code of KitChooser from
      the ProjectExplorer.
      
      Move populate() away from the constructor as not to call
      virtuals from it.
      
      Implement DebuggerKitChooser. It should no longer be
      possible to to choose an invalid kit for debugging
      from the debugger starter dialogs.
      
      Add a protected constructor to DeviceProcessesDialog
      allowing to pass a KitChooser.
      
      Change-Id: I8c683a2da7d69bfbccdc08213cb47d69a0df8b3e
      Reviewed-by: default avatarTobias Hunger <tobias.hunger@nokia.com>
      c3f50e31
  15. 04 Sep, 2012 1 commit
    • Tobias Hunger's avatar
      s/profile/kit/ · 8ba422d0
      Tobias Hunger authored
      * Rename profiles to kits.
      * Update some strings:
         * projects mode has a Kits tab, not a Targets tab.
         * " Settings" was dropped from the sub-tabs of the Kits tab
         * menu entry "Build/Open Build/Run Target Selector" was renamed
           to "Build/Open Build and Run Kits Selector".
         * Use "Kit" instead of "Target" in miniprojecttargetselector.
           (The class was not renamed as it does indeed select targets,
            not kits)
      
      Change-Id: I0727e086e2dfa0e8aaaf89fdc6f2e3596c7a4314
      Reviewed-by: default avatarEike Ziller <eike.ziller@nokia.com>
      8ba422d0
  16. 03 Aug, 2012 1 commit
  17. 24 Jul, 2012 1 commit
  18. 19 Jul, 2012 1 commit
  19. 18 Jul, 2012 1 commit
  20. 17 Jul, 2012 1 commit
  21. 28 Jun, 2012 1 commit
  22. 27 Jun, 2012 1 commit
  23. 26 Jun, 2012 1 commit
  24. 15 Feb, 2012 1 commit
  25. 26 Jan, 2012 1 commit
  26. 03 Nov, 2011 1 commit
  27. 06 May, 2011 1 commit
  28. 13 Apr, 2011 1 commit
  29. 16 Mar, 2011 1 commit
  30. 25 Feb, 2011 3 commits
  31. 24 Feb, 2011 1 commit
    • Friedemann Kleint's avatar
      Debugger: Add toolchain combos to start dialogs, refactor detection. · 75f4b9cf
      Friedemann Kleint authored
      Add combo box listing toolchains with debuggers to start external,
      attach and core.
      Another attempt at streamlining engine detection:
      Split in detection functions that first collect a list of
      available engines by preference, then remove disabled and
      wrongly configured engines and use the remaining best.
      matching. checkconfiguration is now the central place where
      engine detection and config check takes place.
      
      Rubber-stamped-by: hjk
      75f4b9cf
  32. 12 Jan, 2011 2 commits
  33. 17 Dec, 2010 1 commit
  34. 08 Nov, 2010 1 commit
  35. 02 Nov, 2010 1 commit
  36. 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