-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InvalidInput for Camera::start with a valid config, only in release mode #18
Comments
On second look, I'm wrong about where the error is coming from - I believe it's alloc_buffers and Specifically, |
I'll try to reproduce your problem as soon as I get my raspberry back. |
I noticed that it does say it sets errno, when printing last_os_error before/after v4l2_mmap, it doesn't change - which doesn't mean it's not working. |
I am seeing a similar error in Camera::start (also cross-compiling to Pi), also only in --release build: I/O error: Value too large for defined data type (os error 75) Strangely enough, if I clone rscam's source locally and build it: [dependencies] everything works just fine. Was the failure fixed since 0.5.4 release? |
Compiling locally on a raspberry pi, also gives an error when compiled with Comparing both strace output the issue happens on the following call:
compared with the debug version:
I'm using the latest version (v0.5.4) |
I've just encountered this cross-compiling to This is version |
When running a
--release
build (no non-standard options),Camera::start
, which functions correctly with debug mode, throws the error:Io(Os { code: 22, kind: InvalidInput, message: "Invalid argument" })
. I cannot adjust the options correctly to get it to not do this, and the options I select do show up when doingcamera.resolution
, etc.As far as I can tell, it derives from here:
https://github.com/loyd/rscam/blob/5e7a429fe1faed82925832c5ea5d3c9dadb6b239/src/v4l2.rs#L87-90
This led me down the path of enabling the
no_wrapper
feature, which did work in release mode, but changed the available formats, frame rates, etc. that it would allow me to use. I assume that differences between release and debug are not intentional, so I'd rather avoid that road.It's worth mentioning that I am cross compiling for
armv7-unknown-linux-gnueabihf
.I'm going to look in to this issue since it does matter to me for my project, but if you have any ideas I'd love any tips you might have?
The text was updated successfully, but these errors were encountered: