From 9e79c6bd97124a48991311bfa6ab0a4baaf8656e Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Sun, 26 Mar 2017 18:39:08 +0200 Subject: [PATCH] Fix release date --- blog/content/post/09-handling-exceptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/post/09-handling-exceptions.md b/blog/content/post/09-handling-exceptions.md index bb871069..027ec8b4 100644 --- a/blog/content/post/09-handling-exceptions.md +++ b/blog/content/post/09-handling-exceptions.md @@ -1,6 +1,6 @@ +++ title = "Handling Exceptions" -date = "2017-03-09" +date = "2017-03-26" +++ In this post, we start exploring CPU exceptions. Exceptions occur in various erroneous situations, for example when accessing an invalid memory address or when dividing by zero. To catch them, we have to set up an _interrupt descriptor table_ that provides handler functions. At the end of this post, our kernel will be able to catch [breakpoint exceptions] and to resume normal execution afterwards.