On Tue, Oct 21, 2008 at 08:30:17PM +0200, Francesco Romani wrote: > On Mon, 2008-10-20 at 17:29 -0400, Andrew wrote: > > > > > >I got past this with "MALLOC_CHECK_=1" > > > > > > > Profuse apologies. Better to correct myself now, than mislead some poor > > newbie soul later. > > > > I set the MALLOC_CHECK_ variable to "0", not "1", for the glibc mess to go > > away. > > Wait, doing like that You're just hiding the syntomps, not curing the > problem. > The backtrace automatically spit out by glibc seems to end into libav* > libraries, so it doesn't look a problem of transcode (...yet). > I'll try to replicate your bug as soon as I can. > > In the meantime, upgrading libav* could definitively solve your problem.
Thanks, Franceso. I don't know what you are referring to by "libav*" rpm -qa | grep libav libavc1394-0.5.3-2.fc9.x86_64 yum search libav Loaded plugins: refresh-packagekit ====================== Matched: libav =========================== libavc1394.i386 : Audio/Video Control library for IEEE-1394 devices libavc1394.x86_64 : Audio/Video Control library for IEEE-1394 devices libavc1394-devel.i386 : Development libs for libavc1394 libavc1394-devel.x86_64 : Development libs for libavc1394 none of the above seem to be relevant. thanks andrew
