rust-osdev / rust-osdev/bootloader
Mapping the kernel's own debug symbols
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.7k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Description
There could probably be an option to have the bootloader map the kernel's own debug symbols into memory somewhere. A use case for this would probably be profiling from within the OS itself, like what SerenityOS supports, IIRC.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by clarifying the required symbol format, memory layout, and bootloader interface, then identify the kernel-loading path and relevant validation coverage. Done should mean an agreed design and tests demonstrating that the kernel's debug symbols are mapped for OS-level profiling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100