CMAKE_C_FLAGS variable.

Update the command line client with changes made when
adding support for modules to the test framework.

A fix and a test case for
https://bugs.launchpad.net/tarantool/+bug/702397
"If SELECT request specifies tuple count 0, no error"

A check was missing.

Make remote_row_reader_v11 declaration match the definition.

Conflicts:
	test/CMakeLists.txt
	test/lib/tarantool_box_server.py
	test/lib/test_suite.py
	test/test-run.py

Zero index structure before use.

Conflicts:
	test/lib/tarantool_connection.py
	test/lib/tarantool_silverbox_server.py
	test/lib/test_suite.py

	 generalize Server class
	 implement TarantoolServer class
	 implement TarantoolSilverboxServer class
	 implement TarantoolFeederServer class
	 a lot changes in interfaces and bugfixes

Rename box_dispach to box_dispatch.

Define what field data is.

Revert the yesterday's patch that installs SIGCHLD
handler to early collect <defunct> server processes
that received SIGSEGV/otherwise somehow terminated
abnormally.

The invinite loop in Tarantool_connection::recvall()
was caused by misuse of the Python socket API,
not by the fact that the sending side was still
"alive".

The correct fix simply checks for EOF received from
the other end and raises an exception if
we expected some data and got a EOF.

Iron out thet sigchld handler.

If Tarantool server segfaults when a test is
running, it used to hand in <defunct> state,
since there was no wait() call in the parent
to collect child process state. All file descriptors,
as well as open sockets, of a <defunct> process were
left open. This lead to the test runner cycling
in an infinite loop in recv() from the server,
and the whole test suite to, ultimately, hanging
in a busy wait.

This looks more like a bug in python pexpect,
but install a SIGCHLD handler to work it around,
and collect child data immediately as soon as
child terminates.

A fix and a test case for
https://bugs.launchpad.net/tarantool/+bug/730593
"Bad data if incomplete tuple"

A partial tuple could get accepted by INSERT
command, and later on show up in all search results
on the index for which this partial tuple was missing
keys.

When inserting into a TREE index Tarantool/Box did not
validate that the tuple which is being inserted actually
has fields used in the index, and would insert instead
an "ASTERISK" (wildcard) value into the index.

Additionally, when such validation was added, it turned
out that box_raise leaves a corrupt tuple in place
since txn_abort() doesn't remove the unless it's marked
as "GHOST", and tuples were marked as "GHOST" after
index insert, not before.

Conflicts:
	CMakeLists.txt
	core/coro.c
	core/fiber.c
	core/palloc.c
	include/fiber.h

A fix and a test case for

https://bugs.launchpad.net/tarantool/+bug/729758
"SELECT fails with a disjunct and small LIMIT"

and

https://bugs.launchpad.net/tarantool/+bug/729879
"Zero limit is treated the same as no limit"

These were simple coding bugs in SELECT main loop.

Conflicts:
	test/lib/test_suite.py

Allow disjunctions in SELECT WHERE clause and LIMIT
clause in SELECT, to be able to cover the problem
reported in Bug#729758.

Fix a bug with prepare_gdb arguments (remove an extra
space in -e option).

Add a simple test for Bug#729758.

The following bugs were reported in the process:

Bug#729789 "Zero limit is treated the same as no limit"
Bug#730593 "Bad data if incomplete tuple"
Bug#730613 "SELECT with a disjunction on multiple keys returns
matching tuples twice"

We don't have to reset struct sigaction
before every call to sigaction().

Use memset() to zero-initialize sigaction,
since there can be platform-specific memebers.