We’ve been playing with FastMM4 and its debugging capabilities this evening. They are quite impressive: you can get detailed listings of memory leaks with callstack information and see who’s responsible for it, get informed about invalid memory usages and so on. And this without using any additional memory profilers or other tools, you just need to enable the debug mode of FastMM4 and recompile your application. If there are any problems with your application, you then get a log file with detailed reports. Really nice.
We tried it with the SmartInspect Console and just by enabling the debugging functionality of FastMM4 we noticed and fixed a dangling pointer problem of a third-party library. FastMM4 isn’t just a performance wonder, it’s a really useful debugging aid as well.
Debugging with FastMM4
We’ve been playing with FastMM4 and its debugging capabilities this evening. They are quite impressive: you can get detailed listings of memory leaks with callstack information and see who’s responsible for it, get informed about invalid memory usages and so on. And this without using any additional memory profilers or other tools, you just need to enable the debug mode of FastMM4 and recompile your application. If there are any problems with your application, you then get a log file with detailed reports. Really nice.
We tried it with the SmartInspect Console and just by enabling the debugging functionality of FastMM4 we noticed and fixed a dangling pointer problem of a third-party library. FastMM4 isn’t just a performance wonder, it’s a really useful debugging aid as well.