Help¶

This MUST not be used unless you have an hard to catch bug. This will reset the pkt cursor when it’s freed, so any subsequent r/w operations will not segfault, but just bail out and hopefully it will enable you to know who/where the packet was freed already. Do not set this, by any means, unless you are actively debugging.

Direct dependencies¶

NETWORKING

(Includes any dependencies from ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to n.

Symbols selected by this symbol¶

NET_DEBUG_NET_PKT_ALLOC

Kconfig definition¶

At <Zephyr>/subsys/net/ip/Kconfig.debug:36

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:34 → <Zephyr>/subsys/net/Kconfig:87 → <Zephyr>/subsys/net/ip/Kconfig:779

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → IP stack

config NET_DEBUG_NET_PKT_NON_FRAGILE_ACCESS
    bool "Reduce r/w fragility by resetting the packet cursor when freed"
    select NET_DEBUG_NET_PKT_ALLOC
    depends on NETWORKING
    help
      This MUST not be used unless you have an hard to catch bug. This will
      reset the pkt cursor when it's freed, so any subsequent r/w operations
      will not segfault, but just bail out and hopefully it will enable you
      to know who/where the packet was freed already. Do not set this, by
      any means, unless you are actively debugging.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)