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

15,947

Solution 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++.

Solution 2

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.

Share:
15,947
Rob Anderson
Author by

Rob Anderson

Student at TU-BERLIN

Updated on June 16, 2022

Comments

  • Rob Anderson
    Rob Anderson about 2 years

    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 ?