I was not supposed to commit the function with the name pymonotonic_new(). I
forgot to rename it.

Don't check anymore at runtime that the monotonic clock doesn't go backward.
Yes, it happens. It occurs sometimes each month on a Debian buildbot slave
running in a VM.

The problem is that Python cannot do anything useful if a monotonic clock goes
backward. It was decided in the PEP 418 to not fix the system, but only expose
the clock provided by the OS.

BaseTest now ensures that unittest.TestCase.assertWarns() uses the same
warnings module than warnings.catch_warnings(). Otherwise,
warnings.catch_warnings() will be unable to remove the added filter.

when the test is interrupted (or fail).

Mention also the detected GDB version on verbose mode and on error (if the
major version is smaller than 7).

Also fixes error in 'kill' target (already fixed in 2.7, somehow the fix
didn't make it to this branch).

Patch from Mattip.

on Windows and Cygwin.  Patch from Akira Li.

Patch from Berker Peksag.

Patch from Berker Peksag.

Patch by tagatac

Patch by Mark Roseman.