On Fri, Jul 31, 2015 at 9:23 AM, Thiago Macieira
wrote:
> On Thursday 30 July 2015 22:03:22 rpzrpz...@gmail.com wrote:
> > Thiago:
> >
> > You were right.
> >
> > string.h -> Correct
> >
> > For SIGBUS exceptions, I had some structure members that did NOT
> > end on even 4 byte boundaries.
> >
>
On Thursday 30 July 2015 22:03:22 rpzrpz...@gmail.com wrote:
> 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
> alignm
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
auto
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 decl
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
Does not matter if Debug (O0) or Release (
