Hello, I have done several tests with gdb and put the output here:
[EMAIL PROTECTED]:/raid/capture> gdb --args dvgrab -showstatus -s 0 newyork GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/local/bin/dvgrab -showstatus -s 0 newyork [Thread debugging using libthread_db enabled] Found AV/C device with GUID 0x0800460102e6c66d [New Thread 0xb7c3c6c0 (LWP 21156)] [New Thread 0xb1295b90 (LWP 21159)] [New Thread 0xb09f3b90 (LWP 21160)] Warning: Cannot set RR-scheduler Warning: Cannot disable swapping Capture Started "newyork001.dv": 31.86 MiB 232 frames timecode 45:85:85.45 date 2008.10.16 15:52:10 Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb09f3b90 (LWP 21160)] 0x78787868 in ?? () (gdb) thread apply all bt Thread 3 (Thread 0xb09f3b90 (LWP 21160)): #0 0x78787868 in ?? () #1 0xb7f220b8 in ?? () from /usr/lib/libiec61883.so.0 #2 0xb0a7100c in ?? () #3 0x00023280 in ?? () #4 0x00000000 in ?? () Thread 2 (Thread 0xb1295b90 (LWP 21159)): #0 0xb7f5b424 in __kernel_vsyscall () #1 0xb7ec5025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0x0806e7a2 in IEEE1394Reader::WaitForAction (this=0xb773b008, seconds=0) at ieee1394io.cc:244 #3 0x080560ce in DVgrab::captureThreadRun (this=0xbf974898) at dvgrab.cc:962 #4 0x08056621 in DVgrab::captureThread (arg=0xbf974898) at dvgrab.cc:787 #5 0xb7ec14c0 in start_thread () from /lib/i686/cmov/libpthread.so.0 #6 0xb7d1e55e in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb7c3c6c0 (LWP 21156)): #0 0xb7f5b424 in __kernel_vsyscall () #1 0xb7d13ce7 in poll () from /lib/i686/cmov/libc.so.6 #2 0xb7f2d5b0 in avc1394_transaction () from /usr/lib/libavc1394.so.0 #3 0xb7f2e237 in avc1394_vcr_status () from /usr/lib/libavc1394.so.0 #4 0x0806bb6a in AVC::TransportStatus (this=0xb7f2f100, phyID=-516) at ieee1394io.cc:907 #5 0x08054eb1 in DVgrab::done (this=0xbf974898) at dvgrab.cc:1283 #6 0x0806f609 in main (argc=5, argv=Cannot access memory at address 0x5 ) at main.cc:132 #0 0x78787868 in ?? () I can reproduce the behavior quite good, but it will actually only happen every 2 or 3 times. I have reported the bug upstream to the original maintainer as well, since dvgrab/kino crash even when compiled from the latest sources: <https://sourceforge.net/tracker/index.php?func=detail&aid=2153747&group_id=14103&atid=114103> let me add, that in case dvgrab does not segfault, it complain about buffer underrun: Capture Started 15:51:35 "newyork001.dv": buffer underrun near: timecode 45:85:85.45 date ????.??.?? ??:??:?? This error means that the frames could not be written fast enough. 15:51:35 "newyork001.dv": buffer underrun near: timecode 45:85:85.45 date ????.??.?? ??:??:?? This error means that the frames could not be written fast enough. "newyork001.dv": 52.32 MiB 381 frames timecode 45:85:85.45 date 2008.10.16 15:51:41 Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
