<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The unseen hero of OpenBSD :: Forensic wheels</title><link>https://polymathmonkey.github.io/weblog/artifacts/openbsdmalloc/index.html</link><description>The unseen hero of OpenBSD: otto’s malloc What this is about This is me learning about OpenBSD’s malloc.
I try not to do a surface-level overview.
I want to understand the internals better, the data structures, the design decisions, and why those decisions make heap exploitation so much harder.
What malloc actually does Every C program that needs memory at runtime calls malloc.
malloc is a library function. It’s not a syscall – it’s a layer between your code and the kernel.</description><generator>Hugo</generator><language>en-us</language><copyright>All text is licensed under a Creative Commons Attribution 4.0 International License.</copyright><lastBuildDate/><atom:link href="https://polymathmonkey.github.io/weblog/artifacts/openbsdmalloc/index.xml" rel="self" type="application/rss+xml"/></channel></rss>