02-07-2014 09:02 AM
Using LabWindows/CVI 2010, Windows XP. I have a data acquisition program that uses a rather large number of dynamically allocated arrays as buffers. The buffers are used to hold data from DAQmx and are passed and copied to a number of thread-safe queues and other routines. In certain circumstances, when I free one buffer I get a "dynamic memory is corrupt" error, which probably means - from reading the other posts on this topic on this forum - that some buffer was written past its end and corrupted the dynamic memory linked list. Is there any good way to determine exactly <i>which</i> buffer was corrupted? I don't believe that it was the one that I get the error on, it was probably the previous or next one in the chain. I can see the memory chain in the resource window, but I'm not sure how to interpret it.
02-10-2014 05:57 PM
Hi pblase,
Here is an KnowledgeBase article that was written for LabWindows\CVI 6.0 but it still has some valid suggestions for debugging in LabWindows\CVI 2010:
http://digital.ni.com/public.nsf/allkb/862567530005F09C8625632500692F41?OpenDocument
There are three valid suggestions to debug from this article. The only one that does not work still is the Run » Dynamic Memory feature.
07-18-2019 12:48 AM
HI