All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Flanagan <jason@bitcircle.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetoothctl Segmentation Fault on confirm
Date: Tue, 07 Apr 2015 12:39:36 -0400	[thread overview]
Message-ID: <55240848.9000408@bitcircle.com> (raw)
In-Reply-To: <10129831.UNLGbbm0e3@leonov>

Sorry for the wait, I just heard back from my supervisor that the error 
only occurs when we cross compile with the uClibc library. 
(libuClibc-0.9.33.2)
The actual error message is

bluetoothctl[2545]: segfault at 0 ip b7564efd sp bff77324 error 4 in 
libuClibc-0.9.33.2.so[b753f000+4f000]

On 04/03/2015 06:51 AM, Szymon Janc wrote:
> Hi Jason,
>
> On Thursday 02 of April 2015 14:16:59 Jason Flanagan wrote:
>> The issue that i'm currently having with BlueZ 5.29 is that when i say
>> no to confirming a passkey i get a "Segmentation Fault". I've tried
>> multiple times on multiple devices and i get the same result.
>>
>> bluetoothctl
>> [bluetooth]#agent on
>> [bluetooth]#default-agent
>> [bluetooth]# pair XX:XX:XX:XX:XX:XX
>> Attempting to pair with XX:XX:XX:XX:XX:XX
>> [CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
>> Request confirmation
>> [agent] Confirm passkey 080443 (yes/no): no
>> Segmentation fault
> I'm not able to reproduce this. Could you try running bluetoothctl under
> valgrind or gdb and provide full backtrace of crash?
>


  reply	other threads:[~2015-04-07 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 18:16 bluetoothctl Segmentation Fault on confirm Jason Flanagan
2015-04-03 10:51 ` Szymon Janc
2015-04-07 16:39   ` Jason Flanagan [this message]
2015-04-07 18:54     ` Szymon Janc
2015-04-07 20:58       ` Szymon Janc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55240848.9000408@bitcircle.com \
    --to=jason@bitcircle.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.