Modem Man's Tools Page Here you'll get informations and links about my currently active tools, written in C or C++: _CrtDbg for Windows CE - an easy to use code instrumentation Leak Detector prips for Win32 - Debians prips (Print IPs), ported to Win32, whole source and VS2008 project prips for Win32 - Debians prips (Print IPs), ported to Win32, as source patch for 0.9.9 debian source only Syslog4EventLog - an easy to use BSD Syslog API, writing into Win32 EventLog database Here you can support the further development of all above named projects: Donate 10 EUR (recommended for private users) Donate 100 EUR (recommended for commercial users) Donate any amout from 5 EUR to 1.000 EUR my backup of HP printer driver Here you'll get informations and links about my older Open Source Tools: (sorry, currently not all accessible, stay tuned...) Mr.FTP - is a FTP + FTPS (OpenSSL based) Deamon for Win32 and WinCE Status: parked until time TFTPd - is a TFTP Deamon for Win32 and WinCE Status: parked until fun 30 FPS Patch for JA2 1.13 Status: done, avail via JA2 1.13 SVN access PseudoMIPS - a benchmark tool also made for JA2 1.13 Status: done, avail via JA2 1.13 SVN access VSSC - Very Simple Syslog Client also made for JA2 1.13 Status: developed to libLOG (closed sorce for now) MicroHTTPd - Port for Seiko S7600 (iReady) based on micro_httpd by Jef Poskanzer Status: temporarily not avail Quick Unerase for Sharp PC-E500, emergency version, can be your last chance after you deleted a file Quick Unerase for Sharp PC-E500, feature-blown version, install before you delete anything Other Tools for Sharp PC-E500 (drop me a mail, but chances are low, because a virus defender deleted large parts of my PC-500 stuff and I noted this years after last backup was overwritten) Table Driven Assembler for Sharp PC-E500 Status: starved, google for N. Masuichi, he did a better one, or look here: Yuuichi Akagawa's Pocket Computer Archive Create some bad code (or just using your own code of unknown quality). Compile, Link and run it... ... then let CrtDbg for WinCE do its job. Take a look into the Visual Studio IDE output window: Click to the report line, it jumps immediately to the leak point in your source! Click all the report messages to see all lacations of leaks. I'll also find leaked Sockets, Files, streams, GDI objects, Events and so on. Not only alloc/calloc/realloc API is tracked. You can also locate problems with new/delete and new[] / delete [].