Comment # 7 on bug 1199425 from Freek de Kruijf

(In reply to Matthias Brugger from comment #6)
> You will need to load the debug information for your program. Can you have a
> look if you can compile the tool with debug information enabled?
> After that you should be able to connect to the running process and see the
> backtrace with 'bt'.

I have this piece of code in Bluetooth.cpp:

319     #if defined(__linux__)
320
321     int bthConnect(const char *btAddr, const char *loc_btAddr)
322     {
323         struct sockaddr_rc addr = { 0 };
324         struct sockaddr_rc loc_addr = { 0 };
325
326         int status = 0;
327
328         sock = socket(AF_BLUETOOTH, SOCK_STREAM, BTPROTO_RFCOMM);
329
330         // When local BT adapter provided, bind socket to this specific
address
331         if (strlen(loc_btAddr) > 0)
332         {
333             loc_addr.rc_family = AF_BLUETOOTH;
334             str2ba(loc_btAddr, &loc_addr.rc_bdaddr);
335             loc_addr.rc_channel = 1;
336             // Bind the socket to the local BT adapter
337             status = bind(sock, (struct sockaddr *)&loc_addr,
sizeof(loc_addr));
338         }
339
340         if (status == 0)
341         {
342             addr.rc_family = AF_BLUETOOTH;
343             addr.rc_channel = 1;
344             str2ba(btAddr, &addr.rc_bdaddr);
345
346             // Connect to Inverter
347             status = connect(sock, (struct sockaddr *)&addr, sizeof(addr));
348         }
349
350         return(status);
351     }

I did set a breakpoint at line 331. In the attachment you will see the output
on my terminal. I used step (s) or simply Return to step further. At a certain
moment it got stuck, gdb did not return with a prompt.