c - Android NDK: Could a function cause Fatal signal 11 (SIGSEGV)? -


i trying port c application , getting following...

04-18 18:39:05.325: d/djni(4973): starting main doom

04-18 18:39:05.335: d/djni(4973): null check completed

04-18 18:39:05.335: a/libc(4973): fatal signal 11 (sigsegv) @ 0x00000000 (code=1), thread 4998 (thread-141)

of course appears issue these lines here...

jni_printf("starting main app"); if(clen == null)         jni_printf("clen null"); if(args == null)         jni_printf("args null"); jni_printf("null check completed"); main(clen, args); jni_printf("start completed"); 

so because of assuming issue main function. right? not being able fine main function implementation throw error?

i confused because compiles , links fine still error. far can tell (i have logging there not gdb yet) must main function.

other classes

dir1/i_mainsdl.h

#ifndef __i_mainsdl__ #define __i_mainsdl__ extern int main(int argc, char **argv); #endif 

dir1/i_main.c

#include "i_mainsdl.h" ... int main(int argc, char **argv) {   lprintf(lo_always, "starting main function"); } 


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

node.js - Bad Request - node js ajax post -

uitableview - Create and use custom prototype table cells in xamarin ios using storyboard -