<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Memory Allocation and GC From Scratch on Void *Pablogs</title><link>https://pablogs.dev/series/memory-allocation-and-gc-from-scratch/</link><description>Recent content in Memory Allocation and GC From Scratch on Void *Pablogs</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pablogs.dev/series/memory-allocation-and-gc-from-scratch/index.xml" rel="self" type="application/rss+xml"/><item><title>What malloc() does not want you to know</title><link>https://pablogs.dev/posts/post-01-no-malloc/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://pablogs.dev/posts/post-01-no-malloc/</guid><description>&lt;p&gt;&lt;em&gt;Post 1 of 13 — Series: Memory Allocation and Garbage Collection from Scratch&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Every time you write &lt;code&gt;malloc(128)&lt;/code&gt;, something apparently magical happens: the runtime hands you a pointer to 128 bytes of memory nobody else is using. You didn&amp;rsquo;t ask the operating system for permission. You didn&amp;rsquo;t specify &lt;em&gt;where&lt;/em&gt; those bytes should live. They simply appeared. And when you call &lt;code&gt;free()&lt;/code&gt;, they vanish back into the void.&lt;/p&gt;
&lt;p&gt;The magic is a lie.&lt;/p&gt;</description></item></channel></rss>