Hi,
I faced the Valgrind error described in
https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/432477 and
reported it: https://bugs.kde.org/show_bug.cgi?id=330180
But then I also tried v4l version 1.0.1 and it seems to me that the
above mentioned error was corrected, but another exists:
==15368== Syscall param ioctl(generic) points to uninitialised byte(s)
==15368== at 0x439EFB7: syscall (syscall.S:30)
==15368== by 0x4488F52: dev_ioctl (libv4lconvert.c:43)
==15368== by 0x44A0BF1: v4lcontrol_create (libv4lcontrol.c:591)
==15368== by 0x44897FF: v4lconvert_create_with_dev_ops (libv4lconvert.c:217)
==15368== by 0x4037BDF: v4l2_fd_open (libv4l2.c:666)
==15368== by 0x42CB904: (below main) (libc-start.c:260)
==15368== Address 0xbe8c5bc4 is on thread 1's stack
==15368== Uninitialised value was created by a stack allocation
==15368== at 0x44A0161: v4lcontrol_create (libv4lcontrol.c:566)
==15368==
==15368== Syscall param ioctl(generic) points to uninitialised byte(s)
==15368== at 0x439EFB7: syscall (syscall.S:30)
==15368== by 0x4488F52: dev_ioctl (libv4lconvert.c:43)
==15368== by 0x44A02D9: v4lcontrol_create (libv4lcontrol.c:630)
==15368== by 0x44897FF: v4lconvert_create_with_dev_ops (libv4lconvert.c:217)
==15368== by 0x4037BDF: v4l2_fd_open (libv4l2.c:666)
==15368== by 0x42CB904: (below main) (libc-start.c:260)
==15368== Address 0xbe8c6018 is on thread 1's stack
==15368== Uninitialised value was created by a stack allocation
==15368== at 0x44A0161: v4lcontrol_create (libv4lcontrol.c:566)
Is this correct?
Thanks.
--
João M. S. Silva
