feat(libc): implement functional malloc and free#37
Closed
jbreu wants to merge 127 commits into
Closed
Conversation
…interrupt handling
- Updated malloc to allocate 8 extra bytes for a size header. - Implemented free() by retrieving the original pointer and calling realloc(ptr, 0). - This enables practical memory deallocation in userland apps like Doom.
0bde2fb to
09bc828
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Previously,
free()was a no-op stub, causing memory leaks in userland. This PR implements a working memory management lifecycle.Changes
mallocnow reserves an additional 8 bytes at the start of each block to store the allocation size.free(ptr)now retrieves those extra 8 bytes and triggers the kernel deallocation viarealloc(p, 0)(Syscall 20).linked_list_allocatordeallocation logic in the JOS kernel.This is a critical fix for running long-lived or memory-intensive applications in JOS.