|
From: Dean K. <kol...@qw...> - 2004-11-13 04:24:12
|
I haven't really used kino. I need to know exactly how to reproduce the crash. I built kino 0.7.5 and clicked some buttons without causing a crash. It's possible that the crash depends upon the video settings, such as NTSC vs PAL, etc. I might need a video file from you. At 04:24 PM 11/10/2004, Dan Dennedy wrote: >Dean, will you be able to look into this? > >-------- Forwarded Message -------- >From: Georg Ostertag <ge...@os...> >To: kin...@li... >Subject: [Kino-dev] x86_64 crash explored a bit >Date: Wed, 10 Nov 2004 21:18:25 +0100 >Hi, > >I am back again with the crash of kino on x86_64 with >the x86_64 optimized libdv. >I attached a gdb to kino while crashing it. > >that's what I get: > > >Single stepping until exit from function g_main_context_iterate, >which has no line number information. >0x0000002a97bcdbbd in g_main_loop_run () from /opt/gnome/lib64/libglib- >2.0.so.0 >(gdb) >Single stepping until exit from function g_main_loop_run, >which has no line number information. > >Program received signal SIGSEGV, Segmentation fault. >vlc_num_bits_block_x86_loop () at encode_x86_64.S:135 >135 movw (%rdi), %ax >Current language: auto; currently asm >(gdb) >Detaching after fork from child process 6701. >0x0000002a98be5f3d in fork () from /lib64/tls/libc.so.6 >(gdb) detach > > > >using ltrace to follow what's happening, I find as last words >of kino: > > >dv_parse_header(0x00e24a70, 0x2a9b02e010, 2, 0xffffffff, 413) = 1 >dv_parse_packs(0x00e24a70, 0x2a9b02e010, 0, 64, 0x2a9b02e1f0) = >0xd8a6a8ff >_ZNSs4_Rep10_M_destroyERKSaIcE(0x01010700, 0x7fbfffd160, 0x01010718, 0, >2) = 0 >dv_decode_full_frame(0x00e24a70, 0x2a9b02e010, 1, 0x7fbfffd5b0, >0x7fbfffd5a0) = >0 >dv_encode_full_frame(0x01182da0, 0x7fbfffd608, 1, 0x2a9bb2b010, >0x2a9b8e6c10 <un >finished ...> >--- SIGSEGV (Segmentation fault) --- > >So I am pretty shure, that there is some bug in the encoding >part of libdv. >Unfortunately, I have no idea how to fix it... > >Georg |