I updated my VDR Gentoo System. ffmpeg updates from 0.5-r1 to 0.5_p20373. Vdr crash after restarting with: klogd: vdr[1856]: segfault at 20 ip b66d9879 sp b1bff0a0 error 4 in libavcodec.so.52.37.1[b6611000+59d000] I downgraded ffmpeg to 0.5-r1 and everything works fine. I tried all masked version's of ffmpeg - same result. Thank goodness I saved the old ebuild of ffmpeg 0.5-r1 because it's gone from portage now :-( emerge --info is to long for pasting in this bug, because I got a Message that I reached 16Kb message size. I will append it. Reproducible: Always Steps to Reproduce: 1. Update and sync system emerge -NDu world 2. emerge --depclean ; revdep-rebuild -i 3. restart vdr Actual Results: klogd: vdr[1856]: segfault at 20 ip b66d9879 sp b1bff0a0 error 4 in libavcodec.so.52.37.1[b6611000+59d000] Expected Results: none of above Current stable Gentoo ffmpeg version seems buggy: http://developer.berlios.de/bugs/?func=detailbug&bug_id=14990&group_id=5358
Created attachment 232935 [details] emerge --info emerge --info is 24kb long - I cant paste it, because there is a 16KB limit.
please describe exactly how to trigger the segfault and provide a meaningful backtrace: http://www.gentoo.org/proj/en/qa/backtraces.xml
(In reply to comment #2) > please describe exactly how to trigger the segfault and provide a meaningful > backtrace: http://www.gentoo.org/proj/en/qa/backtraces.xml > My hollywood plus card and my old mainboard had an hardware chrash last month. I use now the xine plugin with vdr-fbfe, so I can view much more formats. I tryed to get an new dxr3 card to simulate the error, no chance. I think we can close this bug.
