The idea that the protocol and socktype is part of name resolving in the
libc functions is nuts. We keep the name resolver functions assume
TCP/STREAM and we make sure that when we want to connect to a UDP
service we use the correct UDP/DGRAM set instead. This bug was because
the ->protocol field was not always set correctly.

This bug was only affecting ipv6-disabled non-cares non-threaded builds.

Bug: http://curl.haxx.se/bug/view.cgi?id=3154436
Reported by: "dperham"

In OOM situation. Follow-up fix to commit a9cd4f4e.

Bug: http://curl.haxx.se/mail/lib-2011-01/0079.html
Reported by: Quinn Slack

Only under Windows

CMake/CheckTypeSize.c.in and CMake/CheckTypeSize.cmake were removed in
the previous cmake commit

This makes it possible to skip the call to unit_stop() in such
cases.  Also use Curl_safefree() in unit test 1302 so it will
pass the memory torture test.

The just added speedcheck must not ruin the error code if already set
due to a problem.

The CheckTypeSize module that comes with CMake 2.6.2 and above does
everything we need and also supports cross-compiling.  Avoid duplicating
an older version of it here.  This also fixes a cross-compiling error
because the old line

  include ("${CMAKE_MODULE_PATH}/CheckTypeSize.cmake")

failed because CMAKE_MODULE_PATH is a search path and not a directory.

Signed-off-by: Brad King <brad.king@kitware.com>

Check for speedcheck limits during the state machine traversals

I came up with 33 different ways to call it and verify that it returns the
correct return code.

fail is a new function/macro that a test case can use to indicate a test
failure for cases when the standard macros are not sufficient.

As the function doesn't really use the connectdata struct but only the
SessionHanadle struct I modified what argument it wants.

Bug: https://bugzilla.redhat.com/623663

This check verifies that a pointer contains the correct data.

512 bytes turned out too short for some data, so now we allocate a
larger buffer instead

Bug: http://curl.haxx.se/mail/archive-2011-01/0002.html

The UNITTEST_START and UNITTEST_STOP defines needed to do a new brace
level so that test cases can declare variables fine and still remain
fine C89 code.

The test runner script now knows if unittests can run and the unit test
setup file says it is one. I also made runtests.pl deal with no
<command> tag set, so that the description file can get even simpler.

When configure --enable-debug has been used, all files in lib/ are now
built twice and a separate static library crafted for unit-testing will
be linked. The unit tests in the tests/unit subdir will use that
library.

This is the first approach at doing fairly clean and easy to write and
debug unit tests.

We cannot assume that PATH_MAX will be enough for the remote path name
so allocating room for it is the only sensible approach.

Since some systems don't have PATH_MAX and it isn't that clever to
assume a fixed maximum path length, the code now allocates buffer space
instead of using stack.

Reported by: Samuel Thibault
Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608521

Sending "pwd" as a QUOTE command only sent the reply to the
DEBUGFUNCTION. Now it also sends an FTP-like header to the header
callback to allow similar operations as with FTP, and apps can re-use
the same parser.

The loop condition was wrong so keys larger than 340 bits would overflow
the local stack-based buffer.