I used dvgrab for the first time tonight in an attempt to capture VHS-C video by passing the feed from a VHS-C camcorder, through a Sony DCR-TRV730 DV camcorder, then on to a firewire port. (Doing it this way completely eliminates horizontal sync issues I see when I capture the same video directly from the VHS-C camcorder through a PVR150 using ivtv.) During the first attempt, dvgrab seg faulted when the output file was 623919668 bytes in size. Thinking perhaps I'd exceeded some mysterious internal size limit, I started over and initiated another capture, but this time I set the dvgrab file size limit to 600 megabytes. It got quite a bit farther, but seg faulted on the 7th file. Both times syslog showed the following error: Mar 7 20:02:19 localhost kernel: dvgrab[3973]: segfault at 0000000000000027 rip 0000003774b07e13 rsp 00000000409fff80 error 6 A google search of the above error came up empty. The first attempt produced no error message on the command line, save "Segmentation fault". The second attempt produced this on the command line. (I realized after the fact I was running the capture as root, but that shouldn't matter, should it?) [root@osprey t01]# dvgrab --size 600 t01- Capture Started "t01-001.avi": 599.87 MB 5062 frames timecode 01:01:50.06 date 2006.03.07 20:23:00 "t01-002.avi": 599.88 MB 5062 frames timecode 01:01:50.06 date 2006.03.07 20:25:49 "t01-003.avi": 599.88 MB 5062 frames timecode 01:01:50.06 date 2006.03.07 20:28:38 "t01-004.avi": 599.88 MB 5062 frames timecode 01:01:50.06 date 2006.03.07 20:31:27 "t01-005.avi": 599.88 MB 5062 frames timecode 01:01:50.06 date 2006.03.07 20:34:16 "t01-006.avi": 599.88 MB 5062 frames timecode 01:01:50.06 date 2006.03.07 20:37:04 "t01-007.avi": frame dropped: timecode 01:01:50.06 date 2006.03.07 20:37:39 This error means that the ieee1394 driver received an incomplete frame. Segmentation fault OS and package particulars: [jcliburn@osprey t01]$ yum list installed dvgrab Installed Packages dvgrab.x86_64 1.7-3 installed [jcliburn@osprey t01]$ uname -r 2.6.15-1.1833_FC4 There's plenty of space on the (ext2) filesystem, too; 27.3GB fs size, 3.8 used at the time of the error. Before I embark on the time-consuming journey of tracking this down, I thought I'd stop here first and ask if anyone else has seen this behavior from dvgrab under the given kernel. Thanks, Jay
