DVgrab works fine under kernel 2.6.22. Under 2.6.23, stable version dvgrab-1.8 doesn't capture at all. Command line gives a message like this: ____________ ieee1394io.cc:393: In function "virtual bool raw1394Reader::StartReceive()": "ra w1394_start_iso_rcv( handle, channel )" evaluated to -1005 ____________ The camera starts rolling a few seconds, then stops and this message appears: ____________ "" 0.00 MB 0 frames Capture Stopped ____________ No video is grabed whatsoever. dmesg shows normal ieee1394: Node changed: 0-01:1023 -> 0-00:1023 ieee1394: Node suspended: ID:BUS[0-00:1023] GUID[0800460104c32526] plus this new message: ___________ raw1394: old iso ABI has been removed ___________ I updated dvgrab to unstable 3.0 and it works fine. So I guess we should say: if 1.8 doesn't work anymore and 3.0 does, the later one should be marked stable, not the other way around. Reproducible: Always Steps to Reproduce: 1. Use kernel 2.6.23-r3 (I believe all 2.6.23 would produce same results) 2. Use dvgrab-1.8 3. Try capturing anything from a dv camera Actual Results: Apart from the messages above, the xterm from which I launched dvgrab doesn't respond anymore. lsof shows five PID of commands on dvgrab: some named /dev/null and some with lots of libraries related to dvgrab. Even if I manage to kill the xterm window, the process show as still running, and i must kill them with -9 parameter. Expected Results: I believe version 1.8 should be masked or anotated somehow in portage if this is a permanent error with newer kernels. Also, maybe new version 3.0 should be marked stable, as it seems to work fine. I am on amd64, but also tried x86 (intel core 2 duo). I tried running dvgrab from gdb, even thought i'm not used to this program. It shows: ################### (no debugging symbols found) Failed to read a valid object file image from memory. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b183040cda0 (LWP 28964)] [New Thread 0x40800940 (LWP 28967)] ieee1394io.cc:393: In function "virtual bool raw1394Reader::StartReceive()": "raw1394_start_iso_rcv( handle, channel )" evaluated to -1005 "" 0.00 MB 0 frames Capture Stopped Program received signal SIGINT, Interrupt. [Switching to Thread 0x2b183040cda0 (LWP 28964)] 0x00002b182f509635 in pthread_join () from /lib/libpthread.so.0 #################### That final SIGINT I did myself from the keyboard, or else i wouldn't get gdb interface again. Backtrace shows this: #################### #0 0x00002b182f509635 in pthread_join () from /lib/libpthread.so.0 #1 0x0000000000418dc8 in ?? () #2 0x0000000000410da2 in ?? () #3 0x00002b182fda8374 in __libc_start_main () from /lib/libc.so.6 #4 0x0000000000405559 in ?? () #5 0x00007fff7ba8cb38 in ?? () #6 0x0000000000000000 in ?? () #################### I tried the -ggdb flag, doesn't seem to show a lot of info. Maybe I did something wrong here. Just say if I should try that again.
Created attachment 139123 [details] Strace.log
(In reply to comment #0) > I updated dvgrab to unstable 3.0 and it works fine. So I guess we should say: > if 1.8 doesn't work anymore and 3.0 does, the later one should be marked > stable, not the other way around. good idea, thanks for letting us know about troubles with current stable.
x86 stable
ppc stable
amd64 stable
