From c790a9f7745fe8f0591c3e94150dc5a07b83d0dc Mon Sep 17 00:00:00 2001 From: Juliana Fajardini Date: Thu, 19 Mar 2026 16:14:06 -0300 Subject: [PATCH] userguide/exceptions: update for qa-simulation use The docs still referred to ``debug`` mode. Related to Task #7885 --- doc/userguide/configuration/exception-policies.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/userguide/configuration/exception-policies.rst b/doc/userguide/configuration/exception-policies.rst index 6bbb59ef17..34d03baac5 100644 --- a/doc/userguide/configuration/exception-policies.rst +++ b/doc/userguide/configuration/exception-policies.rst @@ -13,7 +13,7 @@ configuration setting (:ref:`read more`). Some configuration is available directly via the :ref:`stats settings`. For developers or for researching purposes, there are also simulation options -exposed in debug mode and passed via command-line. These exist to force or +exposed in ``qa-simulation`` mode and passed via command-line. These exist to force or simulate failures or errors and understand Suricata behavior under such conditions. See :any:`command-line-exception-policies` for those. @@ -330,6 +330,9 @@ Command-line Options for Simulating Exceptions It is also possible to force specific exception scenarios, to check engine behavior under failure or error conditions. +To enable these, you must build Suricata with ``qa-simulation`` enabled +(``--enable-qa-simulation``). + The available command-line options are: - ``simulate-applayer-error-at-offset-ts``: force an applayer error in the to