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 ad38e76b43a210ae775675161ffa6fe30fe3a1bb..6d20f9e3a15eefcaea61537dc26420d608138f00 100644 (file)
--- 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]
 ```
 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?
 
 Note that the address that caused the segfault is `0x2a`, the hex representation of 42.
 What is happening here?