Now the only thing fuzz_setup.sh does is installing new clang; if system
clang supports -fsanitize-coverage then fuzz_setup.sh is not required.

The script only worked if clang folder was already created.

This triggers a runtime error under integer sanitizer

This was triggering an buffer read overflow with asan.

Make the file executable, fix Windows newlines and fix clang setup.

Hopefully this will allow for better fuzzing coverage

Only fuzz the parser for now.

This downloads a clang build that has support for instrumentation, and also
downloads and compiles libFuzzer.a.

This allows us to have faster fuzz cycles since the fuzzer is in-process.

This should make the test fail on a 32-bit target.

This should make the test fail on a 32-bit target.

Cover empty node case - no XPath query can result in that but it's
possible to create a node set with empty nodes manually.

Add tests for PI erroring exactly at the buffer boundary with
non-zero-terminated buffers (so we have to clear the last character
which changes the parsing flow slightly) and a test that makes sure
parse_embed_pcdata works properly with XML fragments where PCDATA can be
at the root level but can't be embedded into the document node.

The only point was to try to test all paths where we can run out of
memory while decoding something. It seems like it may be impossible to
actually do this given that we can't run all paths as wchar_t size
detection is done at runtime...

This change adds more thorough tests for attribute conversion as well as
some assorted tests that fix gaps in coverage.

This makes sure all .reserve calls failure paths are covered. These
tests don't explicitly test if reserve is present on all paths - this is
much harder to test since not all modifications require reserve to be
called, so we'll have to rely on a combination of automated testing and
sanity checking for this.

Also add more parsing out of memory coverage tests.

Enumerate successfull cases and also cases where the detection stops
half-way and results in a different detected encoding.

Add tests for various corner cases of DOM inspection and modification
routines.

Expand out of memory coverage during XPath parsing and evaluation and
add some other small tests.

Currently this test has very large runtime and relies on the fact that
the first memory allocation error causes the test to terminate. This
does not work with new behavior of running the query through and
reporting the error at the end, so make the runtime reasonable but still
generate enough memory to blow past the budget.

gcov -b surfaced many lines with partial coverage, where branch is only
ever taken or not taken, or one of the expressions in a complex
conditional is always either true or false. This change adds a series of
tests (mostly focusing on XPath) to reduce the number of partially
covered lines.

This test is supposed to test error coverage in different expressions
that are nested in other expressions to reduce the number of never-taken
branches in tests (and make sure we aren't missing any).

By default they are set to Jan 1 1970 which breaks homebrew.

Fixes #124.

The variable is being assigned to but never read when exceptions are
disabled.

Previously the error offset pointed to the first mismatching character, which
can be confusing especially if the start tag name is a prefix of the end tag
name. Instead, move the offset to the first character of the name - that way
it should be more obvious that the problem is that the entire name mismatches.

Fixes #112.

Perl version needed Archive::Zip that for some reason is not installed on WSL by
default. Use this as an opportunity to remove the last Perl script.

This test tests two important invariants:

- Every combination of write flags has to result in a valid document
- Parsing that document and saving the result has to result in identical output

We don't test all flags since parse_no_escapes can intentionally result in
malformed documents and other flags aren't relevant for node output.

Also note that we test both no-whitespace and whitespace version to make sure
we don't have unnecessary whitespace added during formatting.

Some compilers support move semantics but don't support ranged for.