Let the request processor return an error response instead of throwing
an Exception.
Catch a Throwable in the request loop to detect unexpected exceptions.
Decrement number of workers even after receiving exception.
Print java.home and java.class.path properties in debug mode.

Add isError() method to check whether a response is an error response.

Return error response message instead of throwing exception.

InvocationStaticContext.

the resolver, do it where the static context is being used, i.e., in the
GuardHelper and SCGenerator.

SCGenerator, StaticContextMethod: move invocation of the static context
method into the StaticContextMethod class to make the class pull its weight
a bit.

AbstractParser, SnippetParser: source code cleanups related to annotation
processing.

method name, and method descriptor.

This causes problems when the same class is loaded multiple times by
different class loaders. The basic block static context will use CFG
that was made for a different method and will not find instruction
nodes of the new method, leading to all sorts of errors.

Instead, memoize the last CFG along with the corresponding method
node, and if the method node changes, recreate the CFG. This seems
to be enough to avoid regenerating the CFG for the same method.

To some degree, this is the result of poor static context interface
and reuse of a single static context instance for multiple shadows.
This needs to be redesigned some time in future.

When using the compiler (clang) to link object files, passing the
-shared flag is OK, but when talking directly to the linker, the
-dylib flag needs to be used instead.