Reputation: 277
I am doing an application with native code. I have a bug, that sometimes produces this error in the logcat, but not produces runtime error:
06-27 18:14:47.526: A/libc(32659): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 592 (Thread-1045)
I have read at internet and it says that could be produces for native code, in concret for the bad acess to memory.
Someone knows somethig?
Thanks
Upvotes: 2
Views: 2792
Reputation: 1
I had the same error with the same address. After "googeling" for days i was stucked. Today i found the solution (in my case): i use win 8 x64 with eclipse Juno. The problem was solved when i have disabled the UAC from windows. Both the adb.exe and eclipse (in my case) were runned in admin mode. Hope will help someone.
Upvotes: -1
Reputation: 93561
This is a seg fault. Its occurring at address 0, which means you're dereferencing a NULL pointer. Its occuring in libc, so its certainly happening in native code, which may be through you calling it directly or through the framework calling it. That's all you can tell from that one line.
Upvotes: 2