Created attachment 80085 [details]
Android tombstone, contains backtrace
this is my first post on this forum so please don't be rude with me if I didn't follow all the possible rules for posting here.
I know that maybe my question shall be posted somewhere else like stack overflow but I already did that without success. I'll try to be the really accurate in explaining my problem so that you can tell me what's happening and if my guesses are true.
I've developed an Android application that extensively use Bluetooth to make my remtoe terminals communicate; I have a small network made of 4-5 smartphones that exhcange data with eachother.
My application is perfectly working until a random reboot afflict the phones, never at the same time. Sometime this could happen after 40 min, sometime after 4-5 hours.
All the times I get the same error and it points to something wrong into the D-Bus system library that I don't remotely use or interact with. The worst thing is that as far as I know google ships Android with D-Bus v1.4 and I'm starting to believe that it's a bug into the library that is causing this problem.
Can you confirm this?
I'll add as attachment the tombstone (it's like the report built by the system right before rebooting), inside of it you can find the backtrace.
As you can read from the backtrace, something wrong happens into the D-Bus library, this leads to the bluetooth deamon to stop and my application goes into fatal system error that force my system to shutting down the VM.
I'm not asking you to tell me how to fix the code, I just want to know if this is a known bug or something similar.
Thank you in advance,
(In reply to comment #0)
> I'll add as attachment the tombstone (it's like the report built by the
> system right before rebooting), inside of it you can find the backtrace.
> As you can read from the backtrace, something wrong happens into the D-Bus
> library, this leads to the bluetooth deamon to stop and my application goes
> into fatal system error that force my system to shutting down the VM.
This appears to be a bug in bluetoothd, rather than in libdbus: bluetoothd is trying to reply to a message that doesn't have a valid serial number.
Please report this bug to your Android distributor (or whoever provided /system/bin/bluetoothd).