From e677e5d569b69d7b2ce90939a9a7b1aad57cf317 Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Sat, 27 Apr 2019 13:13:41 +0200 Subject: [PATCH] Set publish date --- blog/content/second-edition/posts/04-testing/index.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/blog/content/second-edition/posts/04-testing/index.md b/blog/content/second-edition/posts/04-testing/index.md index aa0f5182..e35114a1 100644 --- a/blog/content/second-edition/posts/04-testing/index.md +++ b/blog/content/second-edition/posts/04-testing/index.md @@ -2,7 +2,7 @@ title = "Testing" weight = 4 path = "testing" -date = 0000-01-01 +date = 2019-04-27 +++ @@ -986,9 +986,3 @@ We now have a test framework that runs in a realistic environment inside QEMU. B ## What's next? In the next post, we will explore _CPU exceptions_. These exceptions are thrown by the CPU when something illegal happens, such as a division by zero or an access to an unmapped memory page (a so-called “page fault”). Being able to catch and examine these exceptions is very important for debugging future errors. Exception handling is also very similar to the handling of hardware interrupts, which is required for keyboard support. - - - - -TODO: -- update date