linux-6.15/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"
245 	  that will include debugging info resulting in a larger kernel image.
256 	  Do not build the kernel with debugging information, which will
306 	bool "Reduce debugging information"
308 	  If you say Y here gcc is instructed to generate less debugging
310 	  need full debugging information (like kgdb or systemtap) won't
311 	  be happy. But if you merely need debugging information to
331 	bool "Compress debugging information with zlib"
346 	bool "Compress debugging information with zstd"
430 	bool "Provide GDB scripts for kernel debugging"
436 	  instance. See Documentation/process/debugging/gdb-kernel-debugging.rst
541 	  larger and slower, but it gives very useful debugging information
582 	  and debugging magic section games, and for seeing which
618 menu "Generic Kernel Debugging Instruments"
625 	  if the system crashes for example during kernel debugging (e.g., you
667 	  debugging files into.  Enable this option to be able to read and
713 menu "Networking Debugging"
717 endmenu # "Networking Debugging"
719 menu "Memory Debugging"
766 	  Enable this to turn on debugging of RCU list heads (call_rcu() usage).
785 	bool "Enable shrinker debugging support"
857 	  Enable VM maple tree debugging information and extra validations.
865 	  Enable VM red-black tree debugging information and extra validations.
979 	bool "Highmem debugging"
1032 	bool "Memory allocation profiler debugging"
1044 endmenu # "Memory Debugging"
1332 menu "Scheduler Debugging"
1346 	  stats may be useful for both tuning and debugging the scheduler
1347 	  If you aren't debugging the scheduler or trying to tune a specific
1363 	  depending on workload as it triggers debugging routines for each
1364 	  this_cpu operation. It should only be used for debugging purposes.
1366 menu "Lock Debugging (spinlocks, mutexes, etc...)"
1374 	bool "Lock debugging: prove locking correctness"
1452 	bool "RT Mutex debugging, deadlock detection"
1459 	bool "Spinlock and rw-lock debugging: basic checks"
1469 	bool "Mutex debugging: basic checks"
1476 	bool "Wait/wound mutex debugging: Slowpath testing"
1494 	bool "RW Semaphore debugging: basic checks"
1497 	  This debugging feature allows mismatched rw semaphore locks
1501 	bool "Lock debugging: detect incorrect freeing of live locks"
1566 	bool "Lock dependency engine debugging"
1591 	  are detected by debugging mechanisms or not. (if you disable
1592 	  lock debugging then those bugs won't be detected of course.)
1633 	bool "Debugging for csd_lock_wait(), called from smp_call_function*()"
1645 	bool "Default csd_lock_wait() debugging on at boot time"
1651 	  default to 1 (basic debugging) instead of 0 (no debugging).
1653 endmenu # lock debugging
1660 	  either tracing or lock debugging.
1668 	bool "Debugging for CPUs failing to respond to backtrace requests"
1691 	  It is also used by various kernel debugging features that require
1722 	bool "kobject debugging"
1725 	  If you say Y here, some extra kobject debugging messages will be sent
1729 	bool "kobject release debugging"
1761 	  is more suitable for kernel debugging. If you care about performance,
1809 	  Enable maple tree debugging information and extra validations.
1867 	  that they can be kprobed for debugging.
1872 	bool "Remote debugging over FireWire early on boot"
1893 	  the debugging host before booting the debug target for debugging.
1898 	  See Documentation/core-api/debugging-via-ohci1394.rst for more information.
1914 	  be used by people debugging the kernel. Note that with PAT support
1932 	  specific access can be used by people debugging kernel drivers.
1941 menu "$(SRCARCH) Debugging"
2813 	  Tests SLUB cache debugging functionality.
3344 	  compilation on or off. This can be used to enable extra debugging