Search Results for "c malloc"

Use own (user) data section for each Linked-List-Element (LLEl) including a fix Identifier which is for search via basic Lnkdlst function (fast ID-part-search, e.g. to find all elements with a specific bit in the ID set). Main list-linkage-change functions: append, insert, delete. - Examples: use of flexible variable ArgList (OnePointerArg, optional valid if not NULL, Argument-Type by ID-Number is easy to get), key-value pairs, build FIFO{queue}/LIFO{stack}, auto-list with max....

MDX is a thread safe memory manager similar to the standard C library's malioc() and free(), except that it allows for some (or all) of the memory to be automatically freed by mark and sweep garbage collection with finalization. It's written in C++ under the Apache license for Windows and Linux on 32 & 64 bit systems. Programs using MDX provide it with a marking callback. The callback performs the marking phase of garbage collection, using MDX's mark() method to actually mark the wanted...

... - Easily profile memory usage and track down memory hawks. - Click-And-Goto-Source support for Visual Studio. - Integrated compatibility for new, new[], delete, delete[], malloc, calloc, realloc, free

DigCC is a simple, easy-to-retarget, C compiler. DigCC handles the main features of the C language, including: - complex data types (arrays, structs, and composition thereof) - dynamic structures (lists, trees, graphs, etc) The current version of DigCC targets the DigMIPS processor, and provides a runtime library with I/O and simplified heap handling (malloc/free).

An EXTREMELY FAST portable thread caching malloc implementation written in C for multiple threads without lock contention based on dlmalloc. Optimised for x86 and x64. Compatible with C++. Can patch itself into existing binaries on Windows.

XMEM Extended C/C++ Dynamic Memory Control and Debug Library: The extended C/C++ Dynamic Memory Control and Debug Library XMEM is a replacement library for malloc/free and new/delete to find memory leaks and other memory related errors in C/C++ code.

libsharedmem is an easy to use C library for handling shared memory blocks on POSIX compatible systems. It also contains malloc()/realloc()/free() -style shared allocation functionality and synchronization primitives. libshmsg adds optionally zero-co

This was my first attempt at a persistent (disk-based) allocator, but I aimed too high, used too many obscure C++ features and it got away from me. You will need the version of v3c mentioned in configure.ac.in to build it. Like I said, it contains lots of really obscure C++, if you're curious. This project isn't being actively maintained anymore - see it's way-cooler C/C++ replacement here at SourceForge - treedb.

DUMA (Detect Unintended Memory Access) is a multi-platform memory debugging library. It can detect memory leaks and buffer overruns (or underruns) in a malloc() / new memory buffer. DUMA is a fork of Bruce Perens' Electric Fence library. sourceforge isn't maintained for many years! suggest you want to look at https://github.com/johnsonjh/duma

The fastest malloc we've seen; works particularly well with threads and STL. Also: thread-friendly heap-checker, heap-profiler, and cpu-profiler.

The debug memory or "dmalloc" library has been designed as a drop in replacement for the system's malloc, realloc, calloc, free and other memory management routines while providing powerful debugging facilities configurable at runtime.

Multiprecision unsigned number template library (MUNTL). The program is intended for the organization of calculations with the big precision for unsigned numbers. Program is very fast because do not use any heap call (new, malloc etc.)

NJAMD (Not Just Another Malloc Debugger) protects against all common dynamic memory bugs, without even relinking your executable. It also provides stack trace information, and eventually will include a full GUI interface. NJAMD NEEDS YOUR HELP!

A debuging library for C++. It does dynamic memory management with malloc and looks for potentiazl problems and leaks. It can also free up all leaked memory at the end of the program. I am currently working on hooking the new and delete keywords to wor