It's magic.

What this operating-systems memory-allocation question tests

This is an easy question about the internal design of dynamic memory allocators, specifically the metadata structures that underpin implementations like glibc's malloc. It targets whether you understand how allocators protect themselves against corruption and misuse.

The question invites you to reason about what happens when a heap is under pressure, when pointers go wrong, or when user code accidentally (or maliciously) overwrites memory. A good answer recognises the role of metadata validation in catching these failures early, rather than allowing silent corruption to propagate. This kind of defensive design is fundamental to robust systems programming.

• Heap metadata and chunk structure
• Integrity checks and corruption detection
• Allocator robustness and failure modes