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

[Peter]

Hello
I have been trying to test Antidote and HealthService in Android 4.0.3.
Built Antidote using android-ndk-r8c under cygwin.
When running in the Android machine it shows Connected and the MAC address and then disconnects.
Looking at logcat it tries to associate (method: association_accept_data_protocol_20601), calls method decode_phdassociationinformation() and in code line 'CHK(pointer->nomenclatureVersion = read_intu32(stream, error));' the following error occurs: Fatal signal 7 (SIGBUS) at 0x00000000 (code=128)...

This error could be from a different compiler, so I also built Antidote using android-ndk-r7 as in your instructions but the error still occurs.

How can I find the origin of this error. where should I look into further...

Thanks for any help
Peter

[Elvis Pfutzenreuter]

Which device is the agent?

It would be a bug in Antidote, but we have not had such problems. SIGBUS
could be unaligned access.

Elvis Pfützenreuter
Senior Architect, Connectivity
e...@signove.com
p: +55 83 3321 6367
c: +55 47 8801 6105
--------------------------------------------------------------------------
CONFIDENTIALITY NOTE: This e-mail is intended only for the person or entity
to which it is addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure.

[googbelo]

Thanks for your answer.

The agent device is a Nonin WristOx2 oximeter. It must be compatible/clone the Onyx but maybe it has some different allignment as you say.

Can I test anything to give you more info on the problem ?

Peter

[nicolas]

I also have te same problem ...

just when I receive associating from sensors, there is the fatal signal 7 (SIGBUS) error ...

I recently upgrade to android 4.1, do you think the changes from android 4.0.3 could provoke this bug ?

[subra...@gmail.com]

I am also getting same error.

Trying to interface Omron 708-BT (Bluetooth) device using Antidote (2.0.0) on Android 4.1.2 (Google Nexus S phone). I have build Antidote using NDK (android-ndk-r8e).  While running on Android phone , it is getting connected and other message shown in the LogCat and then we get the following message 

"W/antidote(1735): associating: accepted data protocol id <20601>"

09-05 13:19:09.625: A/libc(1735): Fatal signal 7 (SIGBUS) at 0x00000000 (code=128), thread 1735 (.health.service)

What could be the issue and how to resolve this?

Here is the LogCat details

**********************************************

09-05 13:17:29.171: W/HST(1849): Connected /com/signove/health/device/1

09-05 13:17:29.171: W/HST(1849): ...00:22:58:35:C2:5F

09-05 13:17:29.175: W/HSS(1735): Sent connected to com.signove.health.service.HealthAgentAPI$Stub$Proxy@42819208

09-05 13:17:29.203: W/HSSHDP(1735): Reader thread

09-05 13:17:35.816: W/HSS(1735): HDP data

09-05 13:17:39.234: W/HSSHDP(1735): Reader thread

09-05 13:17:49.281: W/HSSHDP(1735): Reader thread

09-05 13:17:59.332: W/HSSHDP(1735): Reader thread

09-05 13:18:09.347: W/HSSHDP(1735): Reader thread

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735): data received at plugin

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735): Context @0x511f7410 1:1 addref to 2

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735): andplug get APDU stream

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735):  andplug APDU received 

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735):  communication: current sm(unassociated) 

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735):  associating: processing association request 

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735): associating: association protocol version accepted 

09-05 13:19:09.621: W/antidote(1735): DEBUG   

09-05 13:19:09.621: W/antidote(1735): associating: accepted data protocol id <20601>

09-05 13:19:09.625: A/libc(1735): Fatal signal 7 (SIGBUS) at 0x00000000 (code=128), thread 1735 (.health.service)

09-05 13:19:09.957: W/HST(1849): Service connection closed

[kli...@gmail.com]

Hi 

I`ve found the resolution of that problem - some workaround, just set:

android:debuggable="true" in Your manifest file.

and it starts working.

Regards

Dawid Klimt

[Elvis Pfutzenreuter]

Does it suffice to add this flag in manifest, or you need
to compile with DEBUG=1?

> --
> You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[kli...@gmail.com]

I`ve just add flag into manifest, antidote was left without any changes.

So what about relase version (without debugable) which is crashing?

Did anyone from dev team is able to reproduce it?

Regards

Dawid Klimt

[Elvis Pfutzenreuter]

We have been using it with no problems.

One question: are you using the 2.0.0 package or the Gitorious
version?

On 10/29/13, 6:26 AM, kli...@gmail.com wrote:

I`ve just add flag into manifest, antidote was left without any changes.

So what about relase version (without debugable) which is crashing?

Did anyone from dev team is able to reproduce it?

Regards

Dawid Klimt

W dniu pi�tek, 25 pa�dziernika 2013 15:21:44 UTC+2 u�ytkownik Elvis Pfutzenreuter napisa�:

Does it suffice to add this flag in manifest, or you need
to compile with DEBUG=1?

On Oct 25, 2013, at 9:06 AM, kli...@gmail.com wrote:

> Hi
> I`ve found the resolution of that problem - some workaround, just set:
> android:debuggable="true" in Your manifest file.
> and it starts working.
>
> Regards
> Dawid Klimt
>
> --
> You received this message because you are subscribed to the Google Groups "Antidote: open-source IEEE 11073 stack" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to antidote-lib...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[kli...@gmail.com]

Now I am using gitorious version, but I was testing with 2.0.0 too - causing same crash.

I am using android-ndk-r9-windows-x86, minSdkVersion="14" android:targetSdkVersion="18", with eclipse.

[kli...@gmail.com]

I have found some nice article about memcpy android ndk and gcc

http://jeffq.com/blog/over-aggressive-gcc-optimization-can-cause-sigbus-crash-when-using-memcpy-with-the-android-ndk/

[Elvis Pfutzenreuter]

Great finding! This seems to be the explanation. Antidote does a lot
of memcpy() and unaligned dereferencing when composing and
decoding MDER messages.

Now we have to find some flag that allows unaligned operations, I
guess.