Thiago: You were right.
string.h -> Correct For SIGBUS exceptions, I had some structure members that did NOT end on even 4 byte boundaries. I had to specifically set some memory variables to pass on 4 byte alignments. Don't yet know why the NDK C++ compiler won't align on byte boundaries automatically. Thanks, md On 7/29/2015 10:58 PM, Thiago Macieira wrote: > On Wednesday 29 July 2015 21:20:27 mark diener wrote: >> Hello List: >> >> Ran into Android compiler NDK C++/C issue today. >> >> NDK r10e-osx >> SDK Tools 24.3.3 Api 19 (4.4.2) >> >> Code runs great on OSX and IOS. >> >> But dies with SIGBUS (7) on Android 4.x. >> >> And there are issues of implicit declarations of memcpy and memset >> that > > #include <string.h> > >> Does not matter if Debug (O0) or Release (02) >> >> As I begin to deep dive this tomorrow, maybe someone has come across this? > > Sorry, there's really not enough information in your description. All I can > say right now is "there's a bug in your code". > >> >> This has to be a compiler setting issues since armv7 on android fails while >> armv7/arm64 on IOS 7 ipad mini 1st gen works OK. > > Buggy code can work as you'd expect it to, under some circumstances. > -- No spell checkers were harmed during the creation of this message. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
