Willy Tarreau 469fa2c9d9 MINOR: debug: add a new BUG_ON macro ... We do have some code paths testing for impossible errors that tend to be quite confusing, first for maintenance (what to do on such errors, and how far to guess the bug), second for developers as it tends to hide the main purpose and expectations of these call places. Also most of the time impossible errors are ignored by the callers so the tests are not even usable during debugging. Let's instead implement a BUG_ON macro which takes a condition, which if true, will cause a message to be emitted and optionally to crash the process. Additionally, these calls inserted at various places server as hints and documentation for developers to know that such conditions must absolutely not happen. This is only enabled when DEBUG_STRICT or DEBUG_STRICT_NOCRASH are set. As its name implies, DEBUG_STRICT_NOCRASH only performs the test but does not crash, which can be useful to track some checkpoints. At the moment nothing uses this code.		2019-05-14 17:34:49 +02:00
..
common	MINOR: debug: add a new BUG_ON macro	2019-05-14 17:34:49 +02:00
import
proto	BUG/MEDIUM: connections: Don't forget to set xprt_ctx to NULL on close.	2019-05-13 19:11:38 +02:00
types	CLEANUP: connection: remove the handle field from the wait_event struct	2019-05-13 19:14:52 +02:00