Android (OpenCV) NDK development: 0 xdeadbaad (code = 1) error and disable armeabi and libn

1. After OpenCV is transplanted to android, an error occurs during development: android fatal signal 11 (SIGSEGV) at 0 xdeadbaad (code = 1 ). some people say that AsyncTask is used in the program. It happens that it is actually used in my program. However, after careful research, it is found that if the error is: android fatal signal 11 (SIGSEGV) at 0 xdeadbaad (code = 1). The first check is the local C/C ++ code error. It turns out that the matrix dimension is incorrect during opencv operations, leading to program crash. 2. The APP_ABI = armeabi armeabi-v7a in the original Application. mk file, so there are always two sets of this in the generated libs folder. According to the query, armeabi indicates that the so library is used for general CPU of Arm, while the CPU of v7a supports hardware floating point operation. Therefore, armeabi is versatile but slow, while v7a can fully utilize the v7a CPU capabilities. The Huawei U9200cpu model is OMAP4660 and A9. After checking for half a day, I did not see whether the support does not support hardware floating point operations. After removing armeabi, the original program size is reduced to 2.62 MB. Running well, it seems that slimming is critical. Www.2cto.com 3. When compiling the local library in ndk-build, libnative_camera_r2.2.2.so and r2.3.3.so are always generated, as shown below. The strange thing is that I didn't use the camera module in my local code. Add OPENCV_CAMERA_MODULES: = off to the Application. mk file.