stack backtrace #105

Godones · 2023-02-09T14:07:02Z

Update the stack backtrace method
Turn off the -C force-frame-pointers flag, which may cause unnecessary overhead.
The new method should be able to run normally on the alloc-enabled branch

A simple test looks like this:

[kernel] Panicked at src/mm/page_table.rs:178 translated_str: not implemented
---START BACKTRACE---
0x80010a64 (+638) backtrace
0x80010914 (+188) rust_begin_unwind
0x80021624 (+44) core::panicking::panic_fmt
0x8000fb1c (+364) os::mm::page_table::translated_str
0x800072ee (+44) os::syscall::process::sys_exec
0x800067f4 (+456) trap_handler
---END   BACKTRACE---

Use riscv's code generation rules for stack backtraces. 1. Compile the source code in the first pass to generate an executable file, and use the nm tool to extract symbol information 2. The second pass compiles the source code to link the symbolic information into the executable file. Points to note: 1. backtrace needs to support alloc 2. If the kernel panics before alloc initialization, it will cause an error

chyyuu · 2023-02-15T15:26:10Z

Very Good! @Godones

Godones added 2 commits February 9, 2023 21:46

fix: recover the DISASM flag

e6b253c

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

stack backtrace #105

stack backtrace #105

Godones commented Feb 9, 2023

chyyuu commented Feb 15, 2023 •

edited

stack backtrace #105

Are you sure you want to change the base?

stack backtrace #105

Conversation

Godones commented Feb 9, 2023

chyyuu commented Feb 15, 2023 • edited

chyyuu commented Feb 15, 2023 •

edited