michaelkuc6/blog_os
1
0
Fork 0
mirror of https://github.com/phil-opp/blog_os.git synced 2025-12-16 22:37:49 +00:00
Code Issues Projects Releases Wiki Activity

Correct the filenames in comments for where _start() is. (#488)

Browse Source
This commit is contained in:
Donald Pinckney
2018-10-25 08:29:22 -04:00
committed by Philipp Oppermann
parent 1ed19359b5
commit d6c812ea28
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -26,7 +26,7 @@ A double fault behaves like a normal exception. It has the vector number `8` and
Let's provoke a double fault by triggering an exception for that we didn't define a handler function: Let's provoke a double fault by triggering an exception for that we didn't define a handler function:
```rust ```rust
// in src/lib.rs // in src/main.rs
#[cfg(not(test))] #[cfg(not(test))]
#[no_mangle] #[no_mangle]
@@ -155,7 +155,7 @@ So the CPU tries to call the _double fault handler_ now. However, on a double fa
Let's try it ourselves! We can easily provoke a kernel stack overflow by calling a function that recurses endlessly: Let's try it ourselves! We can easily provoke a kernel stack overflow by calling a function that recurses endlessly:
```rust ```rust
// in src/lib.rs // in src/main.rs
#[cfg(not(test))] #[cfg(not(test))]
#[no_mangle] // don't mangle the name of this function #[no_mangle] // don't mangle the name of this function