GDB talks to targets via a so-called remote protocol. These targets
can be things like gdbserver, ROM monitors on specific hardware boards,
or applications that implement the same protocol.

One noteworthy example of application is QEMU, which implements some
basic GDB Remote commands and also a few extenions of its own.

This initial implementation allows connecting to the remote target,
sending commands and receive results. The API can certainly grow later
based on demand.

Changes from v1:
 * Fix a typo in the REMOTE_MAX_PACKET_SIZE comment
Signed-off-by: NCleber Rosa <crosa@redhat.com>

It turns out that, in some conditions, such as when immediatelly trying
to communicate with a gdbserver process after it is executed, results in
failure.

The reason seems to be that gdbserver itself takes "some" time between
being executed and binding to the TCP port.

While prototyping GDB remote client in pure Python, this kind of race
condition was found.

Now, by default, there will be a 2 seconds timeout and a explicit check
for gdbserver's "ready to use" status.

Changes from v1:
 * added documentation for the __init__ method
Signed-off-by: NCleber Rosa <crosa@redhat.com>

multiplex_test uses sleeptest to check it supplies the values correctly.
This patch uses passtest instead.

For now it uses the same multiplex file and in `test_run_mplex_timeout`
still uses sleeptest, but there is FIXME message to use envtest once
it supports params passing (another pull request)
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

CLoader is C (faster) version of the Loader. In case it's unavailable
it fall-backs automatically to the default Loader.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Instead of creating OrderedDicts and then converting it into
tree structure, this modifies the `mapping` constructor to create
the tree structure directly. This way we only walk through the yaml
file once.

Also remove the `tree_unittest.TestReadYAML` selftest as it lost it's
meaning. Valures are checked in the TestTreeNode selftest.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

When initializing TreeNode we should use the add_child function
in order to set the parent correctly.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

.travis.yml: Run selftests in verbose mode

In case of timeout we might want to get the name of the last running
test, therefor setting verbose mode for them.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

.travis.yml: Return apt-get update

Since we have to install extra packages in the VM, some
of which might have been moved/updated, apt-get update
turns out necessary.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Remove license text from the files that are not essential.

Remove the license text from files inside docs, examples and selftest,
to keep the license text only in relevant parts of the project.

References:

* https://fedoraproject.org/wiki/Packaging:LicensingGuidelines
* https://www.gnu.org/licenses/gpl-howto.htmlSigned-off-by: NRudá Moura <rmoura@redhat.com>

plugins: Use utf-8 encoding in html report

Use utf-8 encoding to write the HTML report to avoid errors on systems
with different localization.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

Sdist fixes

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Making justice to all our contributors, change this
silly instance of myself as the author of the whole
thing. Sorry about that.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Use setuptools's option install_requires, to signal
the dependencies avocado requires for full functionality.
Important for publishing avocado in PyPi [1].

[1] https://pypi.python.org/pypiSigned-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Introduce wrap process inside the tests [V3]

Add documentation manual page part for the command line
feature `--wrapper`.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Add some functional tests to explore the --wrapper feature.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Scripts to use with command line option --wrapper.

* dummy.sh    Do nothing (use as a template).
* strace.sh   Run process on strace, output: strace.log.<pid>
* ltrace.sh   Run process on  ltrace, output: ltrace.log.<pid>
* perf.sh     Record process on perf, output: perf.data.<pid>
* valgrind.sh Run process on valgrind's memcheck, output: valgrind.log.<pid>

Usage:

  avocado run datadir --wrapper examples/wrappers/strace.sh
  avocado run datadir \
              --wrapper examples/wrappers/ltrace.sh:make \
              --wrapper examples/wrappers/perf.sh:datadir \
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Valgrind.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Introduce a new command line option (--wrapper) to wrap
every new process created with help of module `avocado.utils.process`
inside a support script.

Wrappers can be global, so it will wrap every process or
you can set a wrapper to a specific program.

* Set wrapper to ltrace.sh on each process:
    avocado run --wrapper ltrace.sh sometest
* Set wrapper to ltrace.sh and binary myprog:
    avocado run --wrapper ltrace.sh:myprog sometest

You can provide multiples --wrapper options,
but only one global wrapper can be active at time.

For API, the class WrapProcess accepts an optional argument `wrapper`.
If it is defined, then use this parameter as the wrapper script.
If undefined, then it will look for the value inside
`runtime.CURRENT_WRAPPER` and use it.

If `runtime.CURRENT_WRAPPER` is None, then just behave like the
`SubProcess` class.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Reorganize requirements.txt and Travis CI job

Document requirements.txt, split it into 3 files:

 * requirements.txt - Used to install deps for functionality
 * tests-requirements.txt - Used to install deps to test avocado
 * travis-requirements.txt - Used exclusively for Travis CI jobs

Also, clean up and simplify Travis install job section.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Merge branch 'gdb_pre_run_commands' of https://github.com/clebergnu/avocado into clebergnu-gdb_pre_run_commands

Conflicts:
	man/avocado.rst

GDB: support for setting gdb/gdbserver paths [v2]

Introduce example test: passtest

This patch replaces most of the calls to sleeptest in our functional
test with passtest, in an attempt to reduce, without invalidating the
purporse, the time it takes to run them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The idea is twofold:

1) Show that a test passes simply by not failing, and doing nothing
   means it can't fail
2) Where appropriate, use this in our own functional tests to reduce
   the selftest runtime.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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>