[XviD-devel] B-frames encoding code committed

Edouard Gomez xvid-devel@xvid.org
Fri, 19 Jul 2002 15:29:44 +0200


Christoph Lampert (chl@math.uni-bonn.de) wrote:
> If you can reproduce this problem, please try with sad16bi_c instead of
> sad16bi_xmm so we can circle the problem somehow...
> 

Same  error, but  this time  i can  trace the  addresses  of reference
frames. They're both out bounds.

*Program received signal SIGSEGV, Segmentation fault.
*0x43f9aa7a in sad16bi_c (cur=0x448f0430 "778:;<<>@@@BCEFGFFFGHHIJKLLMNPQQRTVXYXZ]`_^^^__^^`acbbccfhjiimghjgkmprppqtuwvzyywytuquzvx~\200\203~tlmqqpopx\177\202\204\204\201\203\205\206\206\211\212\207\210\211\211\211\213\213\213\215\217\220\222\220\216\217\221\222\222\223\221\221\214\214\220\220\217\217\217\217\217\222\224\223\223\223\222\220\220\221\232\230\231\230\233\233\232\235\235\234\231\230\227\227\232\230\223\214\205{knk^RPask_G=Ki|\216¡¢¡\237\226\215|j[QL="..., ref1=0x4925430 <Address 0x4925430 out of bounds>, ref2=0x4b22430 <Address 0x4b22430 out of bounds>, stride=672) at ../../src/motion/sad.c:148

It  might be  caused  by a  wrong  directMV value  and the  get_ref_mv
functions  returns a  nonsense pointer.  But i  cannot help  much more
since i've not the skills to debug MV problems.

Does transcode  cut the  vob files  ? So i  could upload  it on  a web
server and gruel could test with the same tools as i'm testing.

-- 
Edouard Gomez