https://devzone.nordicsemi.com/f/nordic-q-a/7301/how-to-use-valgrind-or-a-similar-tool-to-profile-your-application-fro-memory-leaksHey everyone, I&#39;m developing an application using the PCA10001 board. After a while my app crashes. I think this is due to un-freed memory regions. When writing similar programs for linux I usually use Valgrind to profile my application and find memoryen-USTelligent Community 13Wed, 27 May 2015 16:46:24 GMThttps://devzone.nordicsemi.com/thread/25813?ContentTypeID=1Wed, 27 May 2015 16:46:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d5cfad4d-6f5c-44d0-95cf-c31aee3c5d00maxpaynner<p>I&#39;ll try that thanks :(</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/25812?ContentTypeID=1Wed, 27 May 2015 16:40:37 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e126f30e-7396-4ae6-a267-bf836cfdccaeBill Siever<p>This isn&#39;t quite an answer, but a suggestion --- Perhaps you should consider avoiding dynamic memory if possible. If you aren&#39;t sure how to proceed, I&#39;m sure members of this forum may have suggestions.</p> <p>Most embedded systems of this scale avoid the use of dynamic memory (due to a combination of factors, but the main three are: a) the limited memory available, b) the lack of a true OS/runtime to help manage the memory, and c) the run-time behavior of dynamic memory can be difficult to analyze, which makes it difficult to ensure the application will be suitably robust).</p> <p>If there is some reason you must use dynamic memory, an alternative to a memory profiler would be to add instrumentation code to every memory allocation/deallocation to try to spot problems. This isn&#39;t quite the same as Valgrind, which also tracks access, but it may provide information that would help you spot the problem. (Segger&#39;s Real-Time Terminal is a handy tool for this type of debugging. See Vebjørn&#39;s blog post <a href="https://devzone.nordicsemi.com/tutorials/6/debugging-with-real-time-terminal/">devzone.nordicsemi.com/.../</a> )</p><div style="clear:both;"></div>