CONFIG_DEBUG_HUNT_FOR_ZERO: Catch NULL pointer reads/writes

General informations

The Linux kernel configuration item CONFIG_DEBUG_HUNT_FOR_ZERO has multiple definitions:

Catch NULL pointer reads/writes found in arch/blackfin/Kconfig.debug

The configuration item CONFIG_DEBUG_HUNT_FOR_ZERO:

• prompt: Catch NULL pointer reads/writes
• type: bool
• depends on: (none)
• defined in arch/blackfin/Kconfig.debug
• found in Linux kernels: 2.6.24–2.6.39, 3.0–3.19, 4.0–4.16

Help text

Say Y here to catch reads/writes to anywhere in the memory range from 0x0000 - 0x0FFF (the first 4k) of memory. This is useful in catching common programming errors such as NULL pointer dereferences.

Misbehaving applications will be killed (generate a SEGV) while the kernel will trigger a panic.

Enabling this option will take up an extra entry in CPLB table. Otherwise, there is no extra overhead.

Catch NULL pointer reads/writes found in arch/blackfin/Kconfig

The configuration item CONFIG_DEBUG_HUNT_FOR_ZERO:

• prompt: Catch NULL pointer reads/writes
• type: bool
• depends on: (none)
• defined in arch/blackfin/Kconfig
• found in Linux kernels: 2.6.22–2.6.23

Help text

Say Y here to catch reads/writes to anywhere in the memory range from 0x0000 - 0x0FFF (the first 4k) of memory. This is useful in catching common programming errors such as NULL pointer dereferences.

Misbehaving applications will be killed (generate a SEGV) while the kernel will trigger a panic.

Enabling this option will take up an extra entry in CPLB table. Otherwise, there is no extra overhead.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: