[gst-devel] Debugging memory allocation

[Stefan Kost]

Daniel James Laird schrieb:
> All,
>
> I am having real difficulty debugging memory allocation in my application.
>
> Can anyone help
>
> 1.) How do I enable GST_BUFFER debug to that I can see what is going on
>
> I usually do export GST_DEBUG=XXXX:[1-5] but using GST_BUFFER does not seem to work, I cant find anything in docs etc on how to turn on this debug using env variables.
>
> 2.) I use dynamic library loading and this seems to mean that both memwatch and mtrace are not too useful as I can not get the caller fields to be filled with anything other than a hex address which is not as helpful as I had hoped.
> Using valgrind on a mips platform does not work either.
>
> I would love to know how others are debugging memory leaks etc when using gstreamer on embedded devices.  In the mean time finding out how to get GST_BUFFER debug to come out would be really helpful.
>   
1) Try to run as many usecases on x86 and use valgrind --tool=memcheck ...
2) try to split use cases on the target and compare memory usage
3) try the arm port of valgrind on the target

Stefan
> hope you can help
> Daniel Laird 
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>