linux/lib/Kconfig.debug

130 	  Dynamic debugging is controlled via the 'dynamic_debug/control' file,
207 	  debugging but costs about 70-100K of memory.
212 	bool "Kernel debugging"
244 	  that will include debugging info resulting in a larger kernel image.
255 	  Do not build the kernel with debugging information, which will
304 	bool "Reduce debugging information"
306 	  If you say Y here gcc is instructed to generate less debugging
308 	  need full debugging information (like kgdb or systemtap) won't
309 	  be happy. But if you merely need debugging information to
329 	bool "Compress debugging information with zlib"
344 	bool "Compress debugging information with zstd"
424 	bool "Provide GDB scripts for kernel debugging"
430 	  instance. See Documentation/dev-tools/gdb-kernel-debugging.rst
536 	  larger and slower, but it gives very useful debugging information
566 	  and debugging magic section games, and for seeing which
587 menu "Generic Kernel Debugging Instruments"
594 	  if the system crashes for example during kernel debugging (e.g., you
636 	  debugging files into.  Enable this option to be able to read and
682 menu "Networking Debugging"
686 endmenu # "Networking Debugging"
688 menu "Memory Debugging"
735 	  Enable this to turn on debugging of RCU list heads (call_rcu() usage).
754 	bool "Enable shrinker debugging support"
815 	  Enable VM maple tree debugging information and extra validations.
823 	  Enable VM red-black tree debugging information and extra validations.
937 	bool "Highmem debugging"
970 endmenu # "Memory Debugging"
1231 menu "Scheduler Debugging"
1234 	bool "Collect scheduler debugging info"
1254 	  stats may be useful for both tuning and debugging the scheduler
1255 	  If you aren't debugging the scheduler or trying to tune a specific
1284 	  depending on workload as it triggers debugging routines for each
1285 	  this_cpu operation. It should only be used for debugging purposes.
1287 menu "Lock Debugging (spinlocks, mutexes, etc...)"
1295 	bool "Lock debugging: prove locking correctness"
1381 	bool "RT Mutex debugging, deadlock detection"
1388 	bool "Spinlock and rw-lock debugging: basic checks"
1398 	bool "Mutex debugging: basic checks"
1405 	bool "Wait/wound mutex debugging: Slowpath testing"
1423 	bool "RW Semaphore debugging: basic checks"
1426 	  This debugging feature allows mismatched rw semaphore locks
1430 	bool "Lock debugging: detect incorrect freeing of live locks"
1495 	bool "Lock dependency engine debugging"
1520 	  are detected by debugging mechanisms or not. (if you disable
1521 	  lock debugging then those bugs won't be detected of course.)
1562 	bool "Debugging for csd_lock_wait(), called from smp_call_function*()"
1573 	bool "Default csd_lock_wait() debugging on at boot time"
1579 	  default to 1 (basic debugging) instead of 0 (no debugging).
1581 endmenu # lock debugging
1588 	  either tracing or lock debugging.
1596 	bool "Debugging for CPUs failing to respond to backtrace requests"
1619 	  It is also used by various kernel debugging features that require
1650 	bool "kobject debugging"
1653 	  If you say Y here, some extra kobject debugging messages will be sent
1657 	bool "kobject release debugging"
1689 	  is more suitable for kernel debugging. If you care about performance,
1728 	  Enable maple tree debugging information and extra validations.
1786 	  that they can be kprobed for debugging.
1791 	bool "Remote debugging over FireWire early on boot"
1812 	  the debugging host before booting the debug target for debugging.
1817 	  See Documentation/core-api/debugging-via-ohci1394.rst for more information.
1833 	  be used by people debugging the kernel. Note that with PAT support
1851 	  specific access can be used by people debugging kernel drivers.
1860 menu "$(SRCARCH) Debugging"
2665 	  Tests SLUB cache debugging functionality.
2975 	  compilation on or off. This can be used to enable extra debugging