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

Explain new stack_overflow test in post

Browse Source
This commit is contained in:
Philipp Oppermann
2019-04-25 19:28:52 +02:00
parent cd6223c0ab
commit 34bce0513c
2 changed files with 127 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
blog/content/second-edition/posts/05-cpu-exceptions/index.md
View File

@@ -419,13 +419,12 @@ Let's create a test that ensures that the above continues to work. First, we upd
```rust
// in src/lib.rs
/// Entry point for `cargo xtest`
#[cfg(test)]
#[no_mangle]
pub extern "C" fn _start() -> ! {
init(); // new
init(); // new
test_main();
loop {}
}
```
@@ -453,7 +452,7 @@ Apart from printing status messages through the [serial port], the test invokes
[serial port]: ./second-edition/posts/04-testing/index.md#serial-port
You can try this new test by running `cargo xtest --lib`. You should see `test_breakpoint_exception...[ok]` in the output.
You can try this new test by running `cargo xtest` (all tests) or `cargo xtest --lib` (only tests of `lib.rs` and its modules). You should see `test_breakpoint_exception...[ok]` in the output.
## Too much Magic?
The `x86-interrupt` calling convention and the [`InterruptDescriptorTable`] type made the exception handling process relatively straightforward and painless. If this was too much magic for you and you like to learn all the gory details of exception handling, we got you covered: Our [“Handling Exceptions with Naked Functions”] series shows how to handle exceptions without the `x86-interrupt` calling convention and also creates its own IDT type. Historically, these posts were the main exception handling posts before the `x86-interrupt` calling convention and the `x86_64` crate existed. Note that these posts are based on the [first edition] of this blog and might be out of date.