From: Ralf Jung <post@ralfj.de>
Date: Sat, 26 Jul 2025 08:15:02 +0000 (+0200)
Subject: emphasize that this is not a Go panic
X-Git-Url: https://git.ralfj.de/web.git/commitdiff_plain/5a688568dc1005440079571380694ecaf1170971

emphasize that this is not a Go panic
---

diff --git a/personal/_posts/2025-07-24-memory-safety.md b/personal/_posts/2025-07-24-memory-safety.md
index ad38e76..6d20f9e 100644
--- a/personal/_posts/2025-07-24-memory-safety.md
+++ b/personal/_posts/2025-07-24-memory-safety.md
@@ -70,6 +70,7 @@ If you run this program (e.g. on the [Go playground](https://go.dev/play/p/SC-o_
 panic: runtime error: invalid memory address or nil pointer dereference
 [signal SIGSEGV: segmentation violation code=0x1 addr=0x2a pc=0x468863]
 ```
+This is a segfault, not a normal Go panic, so something has gone horribly wrong.
 Note that the address that caused the segfault is `0x2a`, the hex representation of 42.
 What is happening here?