Keeping a close eye on application memoryBy Chris Williams. Published: 6th Sep 2002, 20:36:00 | Permalink | Printable
MalCheck author Erik explains how his handy library worksEarlier this week we reported on MalCheck, a C library for programmers developed by Erik Groenhuis. Erik got back to us recently to tell us about his software and this is what he had to say for himself.
"MalCheck is a system that enables the C programmer to trace problems with malloc blocks", explains Erik. "It consists of a library and a header file. Macros are used to intercept calls to malloc(), free(), realloc() and calloc(). Some extra data is set up to keep track of the allocated blocks. The existing blocks are checked for any signs of corruption. A backtrace of active functions at the time of the call is shown for each block, assisting the user in pinpointing the problem.
"This library came into being because Dr. Smith's excellent MemCheck system could only link with the standard Stubs Clib. Lots of software ported from the GNU environment requires linking with the UnixLib library, so Dr. Smith's can not be used for that. MalCheck offers a freeware alternative, albeit a very much simpler one."
Erik is also the author of RCS for RISC OS.
Previous: The web at your finger tips
Next: Omega sighted in Scotland
DiscussionViewing threaded comments | View comments unthreaded, listed by date | Skip to the end
No comments posted - yet. Post one yourself or come back soon.
Please login before posting a comment. Use the form on the right to do so or create a free account.
Search the archives
Today's featured article
Drobe Special Projects
2 comments, latest by piemmm on 21/10/03 12:23PM. Published: 23 Jul 2003
Programming library DrWimp updated
Improved printing and JPEG handling plus more
Discuss this. Published: 6 Apr 2008
News and media:
RISCOS Ltd •
RISC OS Open •
MW Software •
Advantage Six •
CJE Micros •
Liquid Silicon •
Chris Why's Acorn/RISC OS collection •
The Register •
The Inquirer •
Apple Insider •
BBC News •
Sky News •
Google News •