-
Description[Provide a clear and concise description of the problem. Include any relevant details about the circumstances under which the issue occurred.] Steps to Reproduce
Expected Behavior[Describe what you expected to happen.] Actual BehaviorI have installed motion by `Thread 4 "ml1" received signal SIGSEGV, Segmentation fault. #1 0x00424f12 in memcpy (__len=, __src=, __dest=0xabc99008) at /usr/include/arm-linux-gnueabihf/bits/string_fortified.h:34 #2 v4l2_pix_change ( #3 v4l2_next (cnt=0x4778a0, img_data=0x47ab58) at video_v4l2.c:1809 #5 motion_loop (arg=0x4778a0) at motion.c:2791 #6 0xb5a3b9d8 in start_thread (arg=0x134307d8) at pthread_create.c:477 #7 0xb59d494c in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from /lib/arm-linux-gnueabihf/libc.so.6 It seems like a memcpy error.But Why? Versions
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
FWIW, I run self-compiled motion on OrangePi Armbian with USB camera, no issues. |
Beta Was this translation helpful? Give feedback.
-
I kwon the reason,cause I did not use a release version |
Beta Was this translation helpful? Give feedback.
I kwon the reason,cause I did not use a release version