Greetings,
I have a problem whose solution I can not find.
Recently I have received the following issue report: https://github.com/ftylitak/qzxing/issues/117 . It regards to the usage of QZXing library along with Felfo framework. After downloading the provided example that is said to be crashing ( https://github.com/frankipl/qzxing_test_felgo ) , downloading the latest Felgo for Qt 5.12.3, Android armv7, I confirmed that it is indeed crashing with Segmentation fault. After a number of tries with the debugger and a physical smartphone, it seems like the application gets crashed in a class of QZXing library.
First crash seems to be https://github.com/frankipl/qzxing_test_felgo/blob/aeedf02e708c4eac06654f9f7501406e828f6ce3/QZXing/zxing/zxing/common/GlobalHistogramBinarizer.cpp#L58 . For sanity reasons the reference is replaced by a pointer:
from:
LuminanceSource& source = *getLuminanceSource();
to:
Ref<LuminanceSource> source = getLuminanceSource();
After this change, the next crash gets triggered when a custom exception is thrown in the library (which is a normal operation based on the implementation of the QZXing library).
At this line the exception is thrown as expected: https://github.com/frankipl/qzxing_test_felgo/blob/aeedf02e708c4eac06654f9f7501406e828f6ce3/QZXing/zxing/zxing/common/GlobalHistogramBinarizer.cpp#L188
though this leads to:
F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xe in tid 25507 (Thread (pooled)), pid 25142 (Qzxingtestfelgo)
The same application, without using Felgo works properly as it is reported by the user ( https://github.com/frankipl/qzxing_test ).
Do you have any idea how the combination of Felgo and QZXing could cause such a change at the behavior?
Kind regards
Nikos Ftylitaks