AI-assisted root cause analysis of a null pointer crash: changing a kernel parameter can make NULL writes not report an error
Understand this story
A JavaScript developer used AI to locate the root cause of a null pointer dereference crash in a C program: the kernel parameter DEFAULT_MMAP_MIN_ADDR defaults to 4096, which leaves the first 4096 bytes of memory unmapped, so accessing them triggers SIGSEGV. After setting DEFAULT_MMAP_MIN_ADDR to 0 and recompiling the kernel, the developer's sample program successfully wrote to and read back 42 from a NULL pointer without reporting an error. This result comes only from that sample program and does not mean all null pointer dereferences will stop crashing as a result.
AI overview based on source reports · Updated 7 hr ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Hacker News AIAI resolved all null pointer dereferences in C
A satirical post in which a JavaScript developer argues that writing to NULL should be legal, then has AI identify the kernel's DEFAULT_MMAP_MIN_ADDR=4096 setting as the cause of page faults on the first 4096 bytes. The author recompiles the kernel with DEFAULT_MMAP_MIN_ADDR=0 and links a static binary at address 0, after which a program that dereferences a NULL pointer prints "works 42" instead of segfaulting.
Activity for this story
- Current comparable activity
- 8
- Peak comparable activity
- 10Nov 22 15:00
- Change in the past 24 hours
- –
Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.