michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-17 23:07:50 +00:00
Code Issues Projects Releases Wiki Activity

Add source code link to each post

Browse Source
This commit is contained in:
Philipp Oppermann
2019-01-27 17:58:30 +01:00
parent 04d3c134e2
commit 1034c884ac
9 changed files with 22 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
blog/content/second-edition/posts/07-double-faults/index.md
View File

@@ -10,10 +10,11 @@ This post explores the double fault exception in detail, which occurs when the C
<!-- more -->
This blog is openly developed on [Github]. If you have any problems or questions, please open an issue there. You can also leave comments [at the bottom].
This blog is openly developed on [Github]. If you have any problems or questions, please open an issue there. You can also leave comments [at the bottom]. The complete source code for this post can be found [here][post branch].
[Github]: https://github.com/phil-opp/blog_os
[at the bottom]: #comments
[post branch]: https://github.com/phil-opp/blog_os/tree/post-07
## What is a Double Fault?
In simplified terms, a double fault is a special exception that occurs when the CPU fails to invoke an exception handler. For example, it occurs when a page fault is triggered but there is no page fault handler registered in the [Interrupt Descriptor Table][IDT] (IDT). So it's kind of similar to catch-all blocks in programming languages with exceptions, e.g. `catch(...)` in C++ or `catch(Exception e)` in Java or C#.