Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Trusted Contributor
Posts: 102
Registered: ‎05-09-2013
My Device: BB10 Z10
My Carrier: Virgin

Bluetooth GATT Example - unexpected termination

Hi,

I'm trying to connect to a Bluetooth GATT enabled device (Wahoo scale, same as used in the example. I purchased it just for this purpose) ... Soon after several GATT services are connected, the Bluetooth GATT app terminates unexpectedly (crashes) with the following:

...
Unknown event 13 / D3:C2:52:78:98:7B
Unknown event 15 / D3:C2:52:78:98:7B
GATT service connected: "1800"
Unknown event 18 / D3:C2:52:78:98:7B
GATT service connected: "1801"
GATT service connected: "180A"
GATT service connected: "180F"
GATT service connected: "1901"

Process 42590440 (bluetoothgatt) terminated SIGSEGV code=1 fltno=11 ip=00000088 mapaddr=00000000.

Help?

Retired
Posts: 418
Registered: ‎07-18-2012
My Device: Q10
My Carrier: Bell Canada

Re: Bluetooth GATT Example - unexpected termination

Hi,

 

Which build are you using? Which version of the sample? Has it been modified?

 

SIGSEGV signifies that a segmentation fault has happened - the application is trying to access memory that it does not have access to.

 

With the debugger - can you step through until the seg fault happens?

--
Rob is no longer associated with BlackBerry.
Trusted Contributor
Posts: 102
Registered: ‎05-09-2013
My Device: BB10 Z10
My Carrier: Virgin

Re: Bluetooth GATT Example - unexpected termination

Hi! thanks for the prompt reply. Here's the info:

 

BlackBerry Native SDK 10.2

QNX Momentics IDE 10.2.1

BB10 OS: 10.2.0.1371

Device: STL100-3

 

No modifications - I have downloaded the sample straight from the developer site link, and the files are date stamped to Sept 11, 2013. I have ran the sample right after the battery pull to ensure cleanest possible slate, and the same happens.

 

I haven't tried the debugger, as I haven't looked at the code more closely - I thought I first try here. I also have a retail device and I'll try the sample on it.