For backend requests, we do not have the thread local storage of the
client thread available, so trq.req will normally be (nil).

Dump the busyobj back pointers to req/sess/wrk to maximize the
usefulness of panics.

Also reorder the panic by struct busyobj and add some more members
which may or may not be useful (but when we find out, it is likely
too late).

Also move the vmod list dump to the top level.

Noticed when trying to understand if #2667 was also a stack overflow
in the context of #2817

Conflicts:
	bin/varnishd/cache/cache_panic.c

Fixes: 	#2809

Related to #2810

Conflicts:
	lib/libvmod_debug/vmod.vcc

If two blob pointers compare equal, the blobs are both the same and
equal - both being NULL is implied.

will continue looking backwards from 79687f13

Conflicts:
	doc/changes.rst

Now that we include it in cache.h, it is required by vmods

Ref #2813

For healthy == IGNORE, we return before the call to shard_next(), so
at this point we do want to consider health state - and it makes
absolutely no sense to give up a healthy backend in favor of an un-
healthy one anyway.

Fixes #2823

Avoid (potential) issues due to the monotonic clock not advancing for ~10
seconds such as for virtual machine snapshots or migrations.

In such a scenario, we would kill a child after cli_timeout anyway, so
using the same timeout by default for the watchdog also should reduce
the additional risk implied by it.

Ref	#2814

I never thought that I'd have to fix a string concatenation problem in
a BusyBox awk program to generate VT100 code in a container, but here we
are:

echo | awk 'END {print "foo" "" ++a, "foo" ++a}'

should output "foo0 foo1", and for all the ?awk I tested, it does,
except for BusyBox awk who thought funny to output "0 foo1", breaking the
teken_state.h file.

Fixes #2820

Conflicts:
	bin/varnishtest/tests/v00041.vtc

These are the most significant changes for 6.0.2, as far as
I can see.

and make sure the expects in the test are scrupulusly correct.

Ref #2792

Conflicts:
	doc/changes.rst

See details in r02275.vtc for why there isn't a test case for this.

Conflicts:
	bin/varnishtest/tests/v00058.vtc

Counts the number of times we failed a response due to running out of
workspace during delivery.

Conflicts:
	bin/varnishtest/tests/v00058.vtc

As long as we are not queuing any threads, there is no queue to
move. We record the queue marker the first time we notice queuing and
only then see if it doesn't move.

Fixes #2794

The previous code was correct already, but we can make it
clearer that HFP implies OC_F_PASS

Also test explicitly that both HFM and HFP have their objects
slimmed.

Closes #2768

When producing files with "foo > file", always use the pattern:

	foo > file.tmp
	mv file.tmp file

Otherwise program failures end up generating partial content and
make will not even rerun the failing program next time you type make.

Actually clean CLEANFILES in the clean target.

The reference dir is not built, but it should be in the distfile

We use double for all time representations, yet monotonic time,
real time and durations are not to be confused.

Also, we might want to change the representation of time in the
future.

To get an implicit documentation of the semantic type of a time
value and to facilitate working on the latter, we start off by
introducing simple typedefs which neither inply any change nor
offer any type checking. But they pave the way...

Closes #2783

The panic string is added as a JSON string in the output array.