Contact person: Kernel Memory & Interrupt Repairs

Phone:Show

Email:Show

Location: Newalla, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"The kernel is already largely in place, but two areas are blocking further progress:

• Memory management: paging currently fails, triggering a memhost error.
• Core utilities: low-level output routines no longer return any data.
• Interrupt handling: I need confirmation that every vector is wired correctly and fires when expected.

All code compiles and boots; the job is to trace and correct the logic, not to rewrite large portions. Everything must remain consistent with my existing naming scheme—there isn’t a written guide, yet I can walk you through the rules and patterns before you begin.

Workflow I have in mind
1. You review the current repository so you know exactly what you’re taking on.
2. We agree on a clear set of fixes and a realistic timeline.
3. You deliver a cleaned-up diff or pull request that:
• eliminates the memhost paging fault,
• restores fully functional printf-style and lower-level output calls,
• validates the interrupt descriptor table through basic test cases,
• compiles with the current toolchain (GCC, NASM, LD) and boots in QEMU/Bochs without regression.

I will run the build in my usual VM test harness and sign off once the above passes. If you thrive on kernel-level debugging in C/assembly and can respect an existing coding convention, let’s sort these bugs out." (client-provided description)