Erik Schanze <[EMAIL PROTECTED]> writes: > Partly, you got a nice error message. > Could you reproduce the segfault as well?
Yes, I had 1.7-1 installed which segfaulted as well. Then I just looked whether there is a newer version available. > Aha, it seems this bug was fixed in dvgrab 1.8? It looks like it. >> And now dvgrab 1.7-1 works as well. >> > But the bug still exist. Certainly. A segfault is always a bug. Somewhere. > Seems like an udev issue? Not really. Udev did not set the permissions right. But, that is probably more an issue with my configuration. In any case dvgrab should not segfault and let the user know where the problem is - as the new version does. > > The bug, that Hanno filed, occured only, if /dev/raw1394 exists and no > raw1394 module was loaded. > In this case, which usualy never take place, if automatic device node > creation and module loading works fine, it should give an error > message. This is not completely true. I believe the raw1394 module was loaded and /dev/raw1394 was created when I plugged in the camera. Unfortunately /dev/raw1394 had permissions: crw-rw---- 1 root disk 171, 0 Oct 30 14:00 /dev/raw1394 And dvgrab could not access it. The segfault disappeared when I changed the group owner to video and everything was fine. Now, after unloading the raw1394 module I get: [EMAIL PROTECTED]:/data/video/test$ ll /dev/raw1394 ls: /dev/raw1394: No such file or directory [EMAIL PROTECTED]:/data/video/test$ dvgrab --autosplit --timestamp Segmentation fault As you can see dvgrab even segfaults if /dev/raw1394 is not there. Matthias -- Matthias Julius mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
