42-malloc

This project provides a custom implementation of the malloc, free, and realloc functions in C. It's designed to be used as a shared library that can be preloaded to replace the standard library functions.

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Prerequisites

• Docker
• Visual Studio Code with Remote - Containers extension

Setup

1. Clone the repository:

git clone https://github.com/yourusername/42-malloc.git
cd 42-malloc

2. Open the project in Visual Studio Code.

3. When prompted to "Reopen in Container", click "Reopen in Container". This will start the Docker container and set up your development environment. This can take a few minutes the first time you do it.

If you're not prompted, you can also press F1, type "Remote-Containers: Reopen Folder in Container", and press Enter.

Build

Once you're in the Docker container, you can build the project by running:

make

This will compile the C files and create a shared library libft_malloc.so.

Usage

To use the custom malloc, free, and realloc functions, you need to preload the shared library. This can be done specifically for the program being executed as follows:

LD_PRELOAD=$(pwd)/libft_malloc.so ls

Alternatively, you can set the LD_PRELOAD environment variable for the entire terminal session like this:

export LD_PRELOAD=$(pwd)/libft_malloc.so

Now, any program you run in the same terminal session will use your custom memory allocation functions instead of the standard library functions.

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

License

This project is licensed under the MIT License - see the LICENSE.md file for details.

TODO

• block allocation
• single allocation
• single free
• block free
• struct for blockmetadata
• realloc
• make reading/writing in blocks into struct for easier access so that offset and so gets easier
• symbolic link
• make so that when a 255 reagion exists and a below 32 wants to be allocated a new zone for 32 gets created
• fix bash errors
• alignment
• protect against malloc ver max ram or so u know
• getpagesize under OSX or sysconf(_SC_PAGESIZE) under linux
• make functions static so that they can't be accessed from outside of malloc
• write realloc so that it only copies from previous size
• write visualizer that works well
• fix when 256 exist that a 32 byte will be stored inside of that
• check max allocation on linux

---

• sorted zones for "quick" access
• lifetimes
• multithreading
• dynamic allocation
• size_t in max instead of uint32_t
• allignment %8 for f64 and stuff - LATER!!!