Thanks guys!
The problem is that apparently there is a memory leak in the algorithm
library I just ported into my main project and I was wondering if there is a
ready-made tool (like Purify and the kind) to pinpoint it on TI DSP under
Code Composer. Looks like I have to implement something on my own. Thanks
for the references - it will become my starting point :)
Michael
"mlimber" <
[email protected]> wrote in message
news:
[email protected] oups.com...
> Jerry Avins wrote:
>> Mike_33 wrote:
>> > Hi guys!
>> >
>> > Has anybody ever chased memory leaks on TI DSP? Do you know of any
>> > tools to
>> > do so?
>>
>> Troubleshooting software -- presumably your own code -- is a matter of
>> tools and tricks. What specific questions do you have?
>
> Right. For instance, you might use some static analysis tool such as
> PC-Lint (www.gimpel.com), or you might try using Valgrind or similar
> tools (you might need to port them to the DSP, which is probably not
> worth it for one project, but you might more easily port some of your
> C/C++ code to one of their supported platforms). Also, if you're using
> C++, you should make use of the Resource Aquisition is Initialization
> (RAII) technique to manage all dynamically allocated memory (classes
> such as std::auto_ptr and boost::scoped_ptr do this for you, and can
> fairly easily be ported to the DSP compiler).
>
> Cheers! --M
>