How to use dvgrab.

Paul Howarth paul at city-fan.org
Mon Apr 24 11:34:58 UTC 2006


Dan Dennedy wrote:
> Mike Chalmers <mikechalmers70 <at> gmail.com> writes:
>> Kino experienced a segmentation fault.
>> Dumping stack from the offending thread
>>
>> Obtained 10 stack frames.
>> kino [0x8070d38]
>> [0x493420]
>> /usr/lib/libavcodec.so.51(avcodec_default_execute+0x18) [0xda8948]
> 
> This is the Kino lead developer. We are receiving a bunch of bug reports from
> FC5 users (and only FC5 users) just like this. I do not use FC5 and can not
> reproduce it. One user reported disabling SELinux worked for him. I would like
> to know if this workaround works for others as well. Please send email to
> dan at dennedy.org if it did.
> Also, for a Red Hat developer, if this workaround is the case, what does that
> mean? Is SELinux detecting some memory violation in ffmpeg/libavcodec?

Almost certainly, since the memory checks are the only limitations 
SELinux imposes on "unconfieed" processes in FC5.

Perhaps /usr/lib/libavcodec.so.51 was not built on FC5 or not using the 
default RPM %{optflags} for FC5?

Paul.




More information about the users mailing list