cBlocks Crash on iOS
121 views
Skip to first unread message
jogo
Jan 6, 2012, 2:20:01 PM1/6/12
to Programming Nu
Hi,
the following code does work in iOS-Simulator and when debugging
through XCode, but when running on plain device without gdb it gives
an EXC_CRASH (SIGKILL) with no further information:
NuInit();
NSString* script = @"(do () (puts \"called\"))";
id parsed = [[Nu sharedParser] parse:script];
NuBlock* block = [[Nu sharedParser] eval:parsed];
void (^cblock)( ) = [NuBridgedBlock cBlockWithNuBlock:block
signature:@"v"];
cblock();
the following code does work in iOS-Simulator and when debugging
through XCode, but when running on plain device without gdb it gives
an EXC_CRASH (SIGKILL) with no further information:
NuInit();
NSString* script = @"(do () (puts \"called\"))";
id parsed = [[Nu sharedParser] parse:script];
NuBlock* block = [[Nu sharedParser] eval:parsed];
void (^cblock)( ) = [NuBridgedBlock cBlockWithNuBlock:block
signature:@"v"];
cblock();
jogo
Jan 9, 2012, 3:58:43 PM1/9/12
to Programming Nu
So far I was not able to track this down further.
Sometimes the device crash log is including a Dyld Error Message:
TASK_DYLD_INFO failed: (ipc/send) invalid destination port
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? 0x04807000 0 + 75526144
1 App-iOS 0x0004e438 0x48000 + 25656
Any idea what this could be?
Sometimes the device crash log is including a Dyld Error Message:
TASK_DYLD_INFO failed: (ipc/send) invalid destination port
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 ??? 0x04807000 0 + 75526144
1 App-iOS 0x0004e438 0x48000 + 25656
Any idea what this could be?
Reply all
Reply to author
Forward
0 new messages