From: Stefan K. <ko...@im...> - 2004-09-28 12:23:38
|
hi hi, I've been using refdbg [1] since a few days on my project and it helped me a lot. After fixing a lot of ref-count probelms a few persist and they seem to be inside gst at a very low level. Can anyone of the core developers please try it to and either confirm that there are bugs or tell me that I can safely ignore them. Things I have tried are: refdbg -c "btnum=8 ; r0=B:error" gst-launch sinesrc ! osssink refdbg -c "btnum=8 ; r0=B:error" gst-launch sinesrc ! audioconvert ! esdsink refdbg -c "btnum=8 ; r0=B:error" gst-launch fakesrc ! fakesink and then refdbg -c "btnum=8 ; r0=B:error" gdb --args gst-launch fakesrc ! fakesink The "btnum=8" instructs refdbg to print a backtrace with 8 lines and the "r0=..." is a rule that says "break on Error". The error I get it that gst refs something that already has been destroyed. Unfortunately gdb is not able to get a backtrace for whatever reason :-( Ciao Stefan [1] http://refdbg.sf.net -- \|/ Stefan Kost <@ @> private business +-oOO-(_)-OOo------------------------------------------------------ - - - - - | __ Address Simildenstr. 5 HTWK Leipzig, Fb IMN, Postfach 301166 | /// 04277 Leipzig 04251 Leipzig | __ /// Germany Germany | \\\/// Phone +49341 2253538 +49341 30766101 | \__/ EMail st_kost_at_gmx.net kost_at_imn.htwk-leipzig.de | WWW www.sonicpulse.de www.imn.htwk-leipzig.de/~kost/about.html ===-=-=--=---=---------------------------------- - - - - - |