Debugging Memory Leaks on GStreamer by analyzing reference counters: Difference between revisions

Latest revision as of 19:31, 16 October 2012

Revision as of 18:42, 12 August 2010 (view source) Ddompe (talk \| contribs) (Created page with 'Looking for memory leaks in programs is a very challenging problem. This is even more true for embedded systems, since some of the best tools for this aren't always available (li...')		Latest revision as of 19:31, 16 October 2012 (view source) Tfischer (talk \| contribs) (Replaced content with 'See GStreamer Debugging#Look for memory leaks')
(5 intermediate revisions by 2 users not shown)
Line 1:		Line 1:
	~~Looking~~ for memory leaks in programs is a very challenging problem. This is even more true for embedded systems, since some of the best tools for this aren't always available (like valgrind), or are difficult to use on this environment (like compile-time hacks, since you depend on other libraries that you may not be able to recompile).		See [[GStreamer Debugging#Look for memory leaks]]