4. libxslt - libxslt.fallback.diff

During debugging, it came out that most of those errors that used the wrong ``arguments'' were triggered by placing a ``<fallback>'' tag in the wrong position.

When such a tag is found, ``libxslt'' will print an error message due to the fact it reaches an unexpected position in the code.

However, if you use extension tags provided by mod-xslt and the fallback handler, you will see quite a bounce of these errors. If the library was not patched with libxslt.genericerror.diff or mod-xslt not compiled with ``--enable-libxslt-hack'', then each of these error would cause a SEGFAULT (however, this is not my fault), otherwise, an annoying warning is outputted in the logs.

To avoid this warning filling the logs, you can apply libxslt.fallback.diff, which, conforming with ``REC-xslt-19991116.html#fallback'' will make libxslt ignore the presence of such a tag.

4.1. configure - --enable-fallback-wraparound

Another solution to patching the library is to compile mod-xslt passing ``--enable-fallback-wraparound'' as an argument to configure.

Enabling this option will cause some more code to be compiled in mod-xslt. This code will take care of ``stripping down'' the <fallback tags from ``legal'' positions made illegal by mod-xslt usage of the library.

Eg, the patch solves the problem once and forever. This option solves the problem when it is triggered by mod-xslt, which means every time a <fallback tag is found inside a mod-xslt extension tag.