[ CRITICAL ] [ IMPORTANT ] Getting FATAL Error in libc

rammehta · July 14, 2014, 2:54pm

I am using v3.2 alpha release.
I am getting this error for Android :
A/libc(818): Fatal signal 11 (SIGSEGV) at 0x0000000c (code=1), thread 833 (Thread-56)

I followed the NDK Crash Dump. it gives me this :

My iOS Port is working fine with no errors.

Any Idea whats going wrong here ?
[ I think its a segmentation error ]

How to resolve it ?

rammehta · July 14, 2014, 5:44pm

I think this library got updated for this alpha release ( v3.2 ).
I think something messed up in the update.

Edit : it was libcurl for which 3.2 alpha was released and not libc. My bad. Sorry.

rammehta · July 15, 2014, 7:08am

@walzer @zhangxm @Wuhao @slackmoehrle guys hav you seen this post ?

zhangxm · July 15, 2014, 7:25am

How to reproduce it?

rammehta · July 15, 2014, 10:42am

initialise 12-15 sprites from SpriteFrameCache !!!
Thats what i did i got the error…

[ i subclassd my GameSprite from Sprite Class. Used that GameSprite and nothing else ]
[ i have 2 scheduler methods ]
[ i have 3 Touch methods (TouchBegan,TouchMoved,TouchEnded) ]
[ i have used Vector<> extensively with std::vector ]

Thats all there is in my game. And its working fine for iOS.

slackmoehrle · July 15, 2014, 1:44pm

are you using new anyplace in your code? If so where? Can we see some code?

Also, please PM me directly, please don’t directly ping the developers. They have work to do! Let me coordinate these things with you and I can seek help as we need it.

rammehta · July 22, 2014, 8:12pm

No more movement in this post… and in my android PORT… i think i will need to launch my game as iOS only … sad but true …
From now on i hate NDK … thats a worst thing Google Ever developed…NDK is drunk everytime…
Thanks to Apple for giving full support for c++ 11 in xcode + making c++ code work with iOS flawflessly !

slackmoehrle · July 22, 2014, 8:14pm

eclipse or command-line?

rammehta · July 22, 2014, 8:19pm

i used xcode for coding and eclipse for Android deployment

pabitrapadhy · July 22, 2014, 9:03pm

well don’t get frustrated.

There are thousands of games made with cocos2d-x are are extremely successful.
There could have been some issue,

I am sure it will be solved, only patience is required.
Devs and other experts are there to help everyone, it may take a bit long to figure out
but surely something is fishy.

and may i remind you cocos2d-x is cross platform not platform independent
anyways.

I hope it gets figured out soon.
Till then

Happy Coding

reyanthonyrenacia · December 31, 2014, 11:48am

im having the same problem.my images i get from a spritesheet. it’s all working fine in iOS. but when i port it to eclipse for android build damn, it crashes and says "FATAL SIGNAL 11 " libc , , what’s happening? hopefully someday cocos2dx comes up with its own tools for android build and dont have to rely on Eclipse

reyanthonyrenacia · December 31, 2014, 11:53am

im using cocos2dx 3.2

Victor_K · December 31, 2014, 12:40pm

Please show how you create a sprite and how does your resource folder look like in Xcode project? Is it blue?
Another option may be undefined behaviour somewhere in your code that doesn’t show itself on ios, but causes a crash on android. Try checking indexes, instantiation order etc

reyanthonyrenacia · December 31, 2014, 12:49pm

ok wait, i’ll post thE code when i get home, thnx

reyanthonyrenacia · January 5, 2015, 6:51am

I managed to make it work! I dont blame ECLIPSE on this one, it’s just that iOS tolerates my method of displaying sprite like:
(My “KeypadTile” is derived from Sprite )
KeypadTile* keypadbutton = (KeypadTile*)KeypadTile::create(“keypadpic.png”);// I am using Sprite class’ “create” method, not my user-defined method.
addChiled(keypadbutton);

iOS still displays my picture. But when you port that to Android, it doesnt accept such way of coding. so I fixed it. HOW?

I made my own class of displaying a sprite image inside my KeypadClass class.

KeypadTile.cpp

KeypadTile* KeypadTile::createKeypadTileWithFileName(const char *fileName){
//create an object
KeypadTile sprite = new KeypadTile();
//if object created…
// SpriteFrameCache cachetwo = SpriteFrameCache::getInstance();
// cachetwo->addSpriteFramesWithFile(“sunkenbuttons.plist”); // if PNG file and plist file have the same filename
if (sprite->initWithSpriteFrameName(fileName) ) {

    //memory management o perations :)
    sprite->autorelease();
    //show object in the screen
    return sprite;
}
//if up condition has mistakes, safely return NULL
CC_SAFE_DELETE(sprite);
return NULL;

}

then, I used it .

KeypadTile* keypadbutton = KeypadTile::createKeypadTileWithFileName(“keypadpic.png”);
addChiled(keypadbutton);

and voila, no bugs! :D, good for Android and iOS !

I LOVE COCOS2DX!

Scoridd · January 5, 2015, 11:28am

This is your problem. If you subclass Sprite, you must override the create method. This is because…

Sprite* Sprite::create(const std::string& filename, const Rect& rect)
{
    Sprite *sprite = new (std::nothrow) Sprite();

Sprite ‘create’ uses ‘new Sprite()’. You can recast it as (KeypadTile*) but it is not a KeypadTile object, it is a Sprite() object. So you must rewrite the ‘create’ method…

KeypadTile* KeypadTile::create(const std::string& filename, const Rect& rect)
{
    KeypadTile *sprite = new (std::nothrow) KeypadTile();

If you want to be sure, use dynamic_cast<KeypadTile*> then check the result, to make sure you are actually getting a KeypadTile* object.

I’ve found that iOS tolerates this error but Android doesn’t. It is still wrong though so you should always override the create method.

reyanthonyrenacia · January 6, 2015, 1:28am

whoa! thnx for this concepts, I’ll google what ‘override’ means in C++ OOP. hv a great day!
[SOLVED]