Summary: | False positive in v4l2? | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | João M. S. Silva <joao.m.santos.silva> |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED NOT A BUG | ||
Severity: | minor | CC: | tom |
Priority: | NOR | ||
Version: | 3.8.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | reduced testcase |
Description
João M. S. Silva
2014-01-20 01:10:26 UTC
Created attachment 84737 [details]
reduced testcase
It's impossible to say if it's a false positive without examining the source of v4l2_open to see what it is doing. It may be that valgrind needs better support for whatever ioctl it is doing - currently the "generic" handler is being used rather than a custom handler for that ioctl. if you're not able to examine the v4l2 source yourself then I suggest you refer this to the v4l2 developers who will be able to determine if it's a bug in their code or a problem with valgrind, and if the latter will be able to provide more information. João, please feel free to reopen if you have more information about this ioctl. |