Fatal signal 7 (SIGBUS) at 0x00000000 (code=2)
Asked Answered
I

3

12

While using a OSGi Platform on Android i got this errormsg:

Fatal signal 7 (SIGBUS) at 0x595302e0 (code=2)

Fatal signal 7 (SIGBUS) at 0x595302e0 (code=2)

I don't think that my app needs that much space in memory or need a lot of computation power. Its just the OSGi Platform with 20 Bundles.

My app is always restarting after that.

Any ideas ?

Issi answered 25/10, 2012 at 21:43 Comment(3)
Hi m getting same error.. any luck ? libc(16581): Fatal signal 7 (SIGBUS) at 0xab5a4068 (code=2), thread 16590 (FinalizerDaemon)Brittain
no, sorry to say. no progress.Issi
ok :( thnks :) ... can u plz tll me where exactly u gt ths error ?Brittain
S
1

Even I too found a similar problem and happens to be (code=128) with about fault. Seems to be a data alignment error. To solve this issue, I tried putting a code something like this:

    *Data = (*Data)(Temp+i) becomes     
    Temp1 = *(Temp+i);     
    *Data = Temp1;     

Before and into the function call and passed back the data using same above method. It happens that NDK Compiler works differently some how. And NDK was used to code mix of c and c++.

Stanfill answered 6/6, 2013 at 19:4 Comment(0)
M
1

I had the same problem. It caused by a png file in the drawable folder. I just went to see, what the largest picture is, and I found it, deleted it, and replaced it with a more smaller one, and the problem has gone.

Martini answered 28/3, 2014 at 17:36 Comment(0)
J
0

This is a problem with Data Alignment, as is shown by the error code. Some part of your code or the code in the library you're using probably fails to put data structures in the right place - however, this can be caused by a lot of things, such as a function that is supposed to return something but doesn't.

Joinville answered 22/3, 2013 at 21:33 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.