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

The no_mangle attribute is unsafe since Rust 2024

Browse Source
This commit is contained in:
Philipp Oppermann
2025-03-27 15:39:15 +01:00
parent 9345886d44
commit 9753695744
47 changed files with 149 additions and 149 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
blog/content/edition-2/posts/06-double-faults/index.md
View File

@@ -34,7 +34,7 @@ Let's provoke a double fault by triggering an exception for which we didn't defi
```rust
// in src/main.rs
#[no_mangle]
#[unsafe(no_mangle)]
pub extern "C" fn _start() -> ! {
println!("Hello World{}", "!");
@@ -167,7 +167,7 @@ Let's try it ourselves! We can easily provoke a kernel stack overflow by calling
```rust
// in src/main.rs
#[no_mangle] // don't mangle the name of this function
#[unsafe(no_mangle)] // don't mangle the name of this function
pub extern "C" fn _start() -> ! {
println!("Hello World{}", "!");
@@ -422,7 +422,7 @@ Let's start with a minimal skeleton:
use core::panic::PanicInfo;
#[no_mangle]
#[unsafe(no_mangle)]
pub extern "C" fn _start() -> ! {
unimplemented!();
}
@@ -456,7 +456,7 @@ The implementation of the `_start` function looks like this:
use blog_os::serial_print;
#[no_mangle]
#[unsafe(no_mangle)]
pub extern "C" fn _start() -> ! {
serial_print!("stack_overflow::stack_overflow...\t");