Okay so first off I should state that I am trying to go about troubleshooting a memory leak in a fairly large program that I have. The major problem in the troubleshooting is that the memory leak only seems to show up while running as an executable. I think it would be easier to find if I could use the VI profiler, but that isn't an option in executable form.
I digress from that issue for now though. I have currently settled on using the Desktop Execution Trace Tool to try to watch memory allocates/frees to determine which VI is not freeing the required memory. The program however only allows me to view the data, I need to do some sort of comparison to frees/allocates in order to parse the vast amount of data it produces. I tried the export option only to find that it doesn't actually export anything to the file.
So I feel as of now my best bet is to find a way to read the .ttd file that is generated when the trace is saved. That way I can use labview to parse the file and try to find the culprit VI.
Can anyone help with a way to open a .ttd file in labview? (Or another program that can export it text, Google-Fu is failing me.) Also any other tips for locating a memory leak would be much appreciated. (I feel it would be easier to find if I could establish what types of memory management Labview does in development mode vs. executable, but that's another thing I can't find anywhere.)
Thanks in advance!
