Add support for tracking which spinlocks block other spinlocks and
displaying it as part of the logged statistics.
Fix the logged format, the home string was missing.
Register the spinlock even if we are about successfully get the spinlock
we want.

Only save the strings we want, save on processing time when dumping log
records.
For now, the spinlock logging code is always configured, remove last parts
of HAVE_DIAGNOSTIC version.

Add in new file, support/mutex.c.
Merge branch 'develop' into mutex-logging
Merge branch 'develop' into mutex-logging

Conflicts:
	src/conn/conn_stat.c
Move spinlock statistics dump code out of the connection statistics dump
function, we don't want to dump spinlock information on every source we
list.

Use local WT_CONNECTION_IMPL variable instead of S2C.
Output a line even when no spinlocks were blocked, that way the logging
statistics will have roughly the same timeline as other statistics (I
say "roughly", because if the spinlock hasn't yet registered, the
timeline won't match exactly because unregistered spinlocks don't output
anything until they're registered, but over a reasonably long run they'll
be close).

Don't clear the blocked count until configured to do so.
Don't create a report unless both spinlocks are initialized.
Merge branch 'develop' into mutex-logging
fix a typo in a comment.
We're wasting 4B per WT_UPDATE structure (probably won't matter, but it's
not useful, either).
The option is 'pthread', not 'pthread_mutex'.
Add a new spinlock type, "pthread_logging" which configures the code
that adds statistics logging for the blocking patterns of the spinlock
mutexes.

Fix an inconsistency, the docs and configure output said the pthread
mutex option was 'pthread_mutex', it's actually 'pthread'.
Merge pull request #706 from wiredtiger/mutex-logging

Add spinlock logging to statistics.
Merge branch 'mutex-cleanup' into develop