From 5a688568dc1005440079571380694ecaf1170971 Mon Sep 17 00:00:00 2001 From: Ralf Jung Date: Sat, 26 Jul 2025 10:15:02 +0200 Subject: [PATCH 1/1] emphasize that this is not a Go panic --- personal/_posts/2025-07-24-memory-safety.md | 1 + 1 file changed, 1 insertion(+) 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? -- 2.39.5