Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - D index
The Linux kernel configuration item CONFIG_DEBUG_KMEMLEAK
has multiple definitions:
mm/Kconfig.debug
The configuration item CONFIG_DEBUG_KMEMLEAK:
CONFIG_DEBUG_KERNEL && CONFIG_HAVE_DEBUG_KMEMLEAK
Say Y here if you want to enable the memory leak detector. The memory allocation/freeing is traced in a way similar to the Boehm's conservative garbage collector, the difference being that the orphan objects are not freed but only shown in /sys/kernel/debug/kmemleak. Enabling this feature will introduce an overhead to memory allocations. See Documentation/dev-tools/kmemleak.rst for more details.
Enabling SLUB_DEBUG may increase the chances of finding leaks due to the slab objects poisoning.
In order to access the kmemleak file, debugfs needs to be mounted (usually at /sys/kernel/debug).
lib/Kconfig.debug
The configuration item CONFIG_DEBUG_KMEMLEAK:
CONFIG_DEBUG_KERNEL && CONFIG_HAVE_DEBUG_KMEMLEAK
Say Y here if you want to enable the memory leak detector. The memory allocation/freeing is traced in a way similar to the Boehm's conservative garbage collector, the difference being that the orphan objects are not freed but only shown in /sys/kernel/debug/kmemleak. Enabling this feature will introduce an overhead to memory allocations. See Documentation/dev-tools/kmemleak.rst for more details.
Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances of finding leaks due to the slab objects poisoning.
In order to access the kmemleak file, debugfs needs to be mounted (usually at /sys/kernel/debug).
Raw data from LKDDb:
(none)
This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - D index
Automatically generated (in year 2024). See also LKDDb sources on GitLab