Hello Jorge,
On 04/12/2012 01:01 PM, Jorge Izquierdo Ciges wrote:
Look for previous Java exceptions, maybe you'll get more info. From the
trace "signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004" I
think that could be some linking that hasn't been satisfied and
somewhere the pc goes to that address (I used to have those on the
firsts days with gles2 when it didn't load properly). There are some
tools to look where the code was called in the NDK, that could give you
more clues. (I don't think the same addresses apply to my binaries, so i
can't check) For the moment try 3.0 and see if that works in your phone
(it SHOULD be, i'm using that version right now in the Asus
Transformer) That way at least we can know if it's something that has
changed lately.
Cheers.
J. Izquierdo
I have tried upgrading the NDK and the SVN version still crashes in the
same way. Then I have downloaded the 3.0.1 stable from last year and
that one works fine, so it is indeed an OSG problem somewhere :( Good
that I have an 8 core machine so OSG rebuild takes only some 15 minutes ...
If you know how to debug this sort of crash, I am all ears - on normal
Linux application I would see the missing symbol reported on command
line or load it under gdb and check there. However I have no idea how to
debug a library loaded from Java on Android. The normal Eclipse debugger
doesn't show anything, because the process is killed by the OS.
Regards,
Jan
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
