From 233e32b57095f481c5ddc3e12685d75ea494471e Mon Sep 17 00:00:00 2001 From: Philipp Oppermann Date: Mon, 18 Jun 2018 19:35:59 +0200 Subject: [PATCH] =?UTF-8?q?Update=20=E2=80=9Cwhat's=20next=E2=80=9D=20sect?= =?UTF-8?q?ion=20of=20previous=20post?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- blog/content/second-edition/posts/06-cpu-exceptions/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/content/second-edition/posts/06-cpu-exceptions/index.md b/blog/content/second-edition/posts/06-cpu-exceptions/index.md index 70cd46eb..7602315d 100644 --- a/blog/content/second-edition/posts/06-cpu-exceptions/index.md +++ b/blog/content/second-edition/posts/06-cpu-exceptions/index.md @@ -454,7 +454,7 @@ The `x86-interrupt` calling convention and the [`Idt`] type made the exception h [first edition]: ./first-edition/_index.md ## What's next? -We've successfully caught our first exception and returned from it! The next step is to add handlers for other common exceptions such as page faults. We also need to make sure that we never cause a [triple fault], since it causes a complete system reset. The next post explains how we can avoid this by correctly catching [double faults]. +We've successfully caught our first exception and returned from it! The next step is to ensure that we catch all exceptions, because an uncaught exception causes a fatal [triple fault], which leads to a system reset. The next post explains how we can avoid this by correctly catching [double faults]. [triple fault]: http://wiki.osdev.org/Triple_Fault [double faults]: http://wiki.osdev.org/Double_Fault#Double_Fault