Thanks for your answer Minggo
In that case, it is realy some kind of NDK issue, becouse i’ve checked that and in this case:
CCNode* pChild = dynamic_cast<CCNode*>(pObject);
pObject is not null, it does contain pointer. But i think that danvik does not allowed access to , such way, dinamically memory allocated object. And thats why when we try to acces this object we got whis “silent” crash. I may be wrong offcource.
And what will be the final solution? will it be changed back w/o dynamic_cast, or may be there is some way to make it work with it?
P.S. Just now i’ve read intresting thing in cplusplus documentation of NDK:
II.3. Static runtimes:
Please keep in mind that the static library variant of a given C*+ runtime
SHALL ONLY BE LINKED INTO A SINGLE BINARY for optimal conditions.
What this means is that if your project consists of a single shared
library, you can link against, e.g., stlport_static, and everything will
On the other hand, if you have two shared libraries in your project
which both link against the same static
runtime, each one of them will include a copy of the runtime’s code in
its final binary image. This is problematic because certain global
variables used/provided internally by the runtime are duplicated.
This is likely to result in code that doesn’t work correctly, for example:
- memory allocated in one library, and freed in the other would leak
or even corrupt the heap.
- exceptions raised in libfoo.so cannot be caught in libbar.so .
- the buffering of cout not working properly
This problem also happens if you want to link an executable and a shared
library to the same static library.
In other words, if your project requires several shared library modules,
then use the shared library variant of your C*+ runtime.
It looks like we have a secont type of error when exceptions raised in libgame.so cannot be caught in libcocos2d.so.
but after i’ve tryed to change APP_STL := stlport_static to APP_STL := stlport_shared in application.mk and recompile it i’ve got crash on application startup. My skills are not enouth to understand it , so any help will appreciate