Finding memory errors and leaks

If you have ever observed a program running well for a long time (e.g., hours, days) but then it suddenly crashed, it's likely that the program has memory errors. Debugging memory errors can be frustrating; by the time a problem appears (often by crashing your program), the memory corruption may already be widespread, making the problem source difficult to trace.

Analyzing memory usage is a key function in ensuring the quality of your embedded systems. The QNX System Information perspective lets you quickly see your program's memory usage to get an idea of if it's leaking memory badly. The QNX Memory Analysis perspective shows you how your program uses memory and can help you pinpoint memory errors in your development and testing environments.