From 38fe3380291040eb61166988aab167f050fd3e2c Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Tue, 22 May 2018 19:55:38 +0200 Subject: [PATCH] Add a TODO about panic messages to vga buffer post --- blog/content/second-edition/posts/03-vga-text-buffer/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/blog/content/second-edition/posts/03-vga-text-buffer/index.md b/blog/content/second-edition/posts/03-vga-text-buffer/index.md index d6e5a754..a7845337 100644 --- a/blog/content/second-edition/posts/03-vga-text-buffer/index.md +++ b/blog/content/second-edition/posts/03-vga-text-buffer/index.md @@ -638,6 +638,10 @@ When we now insert `panic!("Some panic message");` in our `_start` function, we So we know not only that a panic has occurred, but also the panic message and where in the code it happened. +### Panic Messages + +TODO + ## Summary In this post we learned about the structure of the VGA text buffer and how it can be written through the memory mapping at address `0xb8000`. We created a Rust module that encapsulates the unsafety of writing to this memory mapped buffer and presents a safe and convenient interface to the outside.