https://modsecurity.org/docs/5-troubleshooting/index.htmlDebugging crashes and misbehavior with gdb, and diagnosing the IIS installer.Hugoen-UShttps://modsecurity.org/docs/5-troubleshooting/5-1-debugging/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://modsecurity.org/docs/5-troubleshooting/5-1-debugging/index.htmlThis page contains information about how to debug ModSecurity. This is not a complete guide or a developer guide, this contains basic information that may help the bug reporting process. Sometimes reproducing problems is not easy due to platform specific issues or even configurations. It is even worse when log files do not contain a specific reference to what might be leading ModSecurity to fail (process is killed before log is saved for instance). In this kind of situation we recommend the utilization of tools such as GDB, which is able to acquire details on the faulty function.https://modsecurity.org/docs/5-troubleshooting/5-2-iis-troubleshooting/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://modsecurity.org/docs/5-troubleshooting/5-2-iis-troubleshooting/index.htmlThis topic introduces tools and options to troubleshooting the IIS version of ModSecurity. It covers the installation process but it was not only limited to that. Running the installer in verbose mode ModSecurity installer was created using the Wix Toolset, a popular tool to produce msi installers. The idea of the installer is to provide an easy way to install and configure ModSecurity on a given machine. If one of those (install or configure) fails, the installer aborts and it should revert any changes that it has made on the system.