1. 20 3月, 2015 2 次提交
  2. 18 2月, 2015 1 次提交
  3. 03 2月, 2015 3 次提交
  4. 20 1月, 2015 2 次提交
  5. 17 1月, 2015 2 次提交
    • C
      Distro plugin: implement distro definition file creation · 8128fa82
      Cleber Rosa 提交于
      As a subcommand (option, really) of the plugin command. The generated
      distro file is supposed to be portable and be named canonically based
      on the name, version, release and arch.
      
      Changes from v0:
       * Return proper exit status when required command line arguments are
         missing
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      8128fa82
    • C
      Distro plugin: add a new distro plugin and basic command · 3e42c9d0
      Cleber Rosa 提交于
      At this stage, the distro plugin is very simplistic and prints the
      detected distribution of the current machine. One could algue that
      this is rather useless, but, with the component isolation work this
      command is going to be helpful for troubleshooting purposes.
      
      Also, this plugin is a placeholder where other functionality will
      live, including (but not limited to):
      
       * the ability to create "distro definition" files, akin to
         autotest's autotest-distro-def-create.
       * the ability to view "distro definition" files, akin to
         autotest's autotest-distro-def-view.
       * the ability to download "distro definition" files from a
         repository
       * (maybe) the ability to push a distro definition file to
         avocado-server. This may be delegated to a full blown REST
         client though.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      3e42c9d0
  6. 15 12月, 2014 1 次提交
  7. 11 12月, 2014 2 次提交
  8. 09 12月, 2014 1 次提交
  9. 27 11月, 2014 1 次提交
  10. 25 11月, 2014 2 次提交
    • C
      GDB: let user choose the gdbserver binary to use · 55b6acc3
      Cleber Rosa 提交于
      Developers using Avocado's GDB support may also need to use their custom
      build of gdbserver.
      
      This implements the same logic and options as the previous commit does
      for the GDB binary, including API level changes.
      
      Changes from v1:
         * use `avocado.utils.process.find_command` as the first default
           location for the gdbserver binary, falling back to the hard coded
           default of `/usr/bin/gdbserver` if that fails.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      55b6acc3
    • C
      GDB: let user choose the GDB binary to use · 7c371623
      Cleber Rosa 提交于
      Developers using Avocado's GDB support may need to use their custom
      build of GDB, or simply their system has GDB at a different location.
      So, allow users to optionally specify the path to the GDB binary.
      
      Also, allow GDB API users to pass extra options to GDB via the command
      line.
      
      Changes from v1:
         * use `avocado.utils.process.find_command` as the first default
           location for the gdb binary, falling back to the hard coded
           default of `/usr/bin/gdb` if that fails.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      7c371623
  11. 24 11月, 2014 1 次提交
    • C
      GDB: add `--gdb-prerun-commands` option to GDB plugin · e9181e13
      Cleber Rosa 提交于
      This feature allows custom GDB commands to be executed before the
      actual binary is run. What it can do then, is only limited by the
      user's goals.
      
      This is intended to allow complex applications, such as QEMU,
      to be debugged inside Avocado tests. Configuring GDB for QEMU,
      for example, involves passing signals to the application that
      would otherwise result in an event that would stop the debugger.
      Signed-off-by: NCleber Rosa <crosa@redhat.com>
      e9181e13
  12. 06 11月, 2014 1 次提交
  13. 08 10月, 2014 1 次提交
  14. 06 10月, 2014 2 次提交
  15. 04 10月, 2014 1 次提交
  16. 02 10月, 2014 2 次提交
  17. 29 9月, 2014 1 次提交
  18. 10 9月, 2014 1 次提交
  19. 03 9月, 2014 1 次提交
  20. 29 8月, 2014 1 次提交
  21. 20 8月, 2014 1 次提交