Closed robert-w-gries closed 6 years ago
Seems like it's a more general issue with the allocator calls. I commented out the process.kstack = None
line and saw the same issue come up in a different location.
rxinu::rust_main (multiboot_information_address=2667712) at src/lib.rs:62
62 for i in 0..max_procs {
(gdb) s
63 syscall::create(test_process, format!("test_process_{}", i));
(gdb) s
core::fmt::ArgumentV1::new<i32> (x=0x14ffa0,
f=0x111110 <core::fmt::num::<impl core::fmt::Display for i32>::fmt>)
at /home/rob/.rustup/toolchains/nightly-2017-12-23-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libcore/fmt/mod.rs:309
309 formatter: mem::transmute(f),
(gdb)
310 value: mem::transmute(x)
(gdb)
308 ArgumentV1 {
(gdb)
313 }
(gdb)
core::fmt::Arguments::new_v1_formatted (pieces=..., args=..., fmt=...)
at /home/rob/.rustup/toolchains/nightly-2017-12-23-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libcore/fmt/mod.rs:363
363 pieces,
(gdb)
364 fmt: Some(fmt),
(gdb)
365 args,
(gdb)
362 Arguments {
(gdb)
367 } // Page Fault here
(gdb)
i686
support has been dropped for now. Will re-open this if it's an issue later
rxinu
code that triggers issueError message
Instruction Pointer