From: Johan Hedberg <johan.hedberg@gmail.com>
To: Murat Kilivan <Murat.Kilivan@csr.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Bluetooth Low Energy service crash report - when trying read a HID feature report
Date: Thu, 24 Jul 2014 11:31:16 +0300 [thread overview]
Message-ID: <20140724083116.GB9891@t440s.lan> (raw)
In-Reply-To: <45F17F5803927D43967AFEED068E781E0879A30E@CAMEUREXM02.EUROPE.ROOT.PRI>
Hi Murat,
On Wed, Jul 23, 2014, Murat Kilivan wrote:
> I have successfully connected to a BLE HID (peripheral) device and /dev/hidraw1 file is created. I am able to read raw data successfully from hidraw1. However, when I try to read a feature report from this device, the Bluetooth service crashes. The bluetooth service log and my source code are below.
>
> Enviroments:
> ------------
> Linux Mint-17 KDE
> Kernel 3.13.0-24-generic
> BlueZ 5.21
>
> Output of Bluetooth service:
> ----------------------------
> # bluetooth -d -n
> ...
> ...
> bluetoothd[2610]: profiles/input/hog.c:forward_report() Sending report type 3 to device 0x000C handle 0x1C
> (bluetoothd:2610): GLib-ERROR **: /build/buildd/glib2.0-2.40.0/./glib/gmem.c:103: failed to allocate 4294967295 bytes
4294967295 is the same as (uint32_t) -1 so seems like there might be a
missing error check somewhere. Could you please try to get the full
bluetoothd backtrace by running it through gdb or valgrind? If possible
do this with the latest git version.
Johan
next prev parent reply other threads:[~2014-07-24 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 13:17 Bluetooth Low Energy service crash report - when trying read a HID feature report Murat Kilivan
2014-07-24 8:31 ` Johan Hedberg [this message]
2014-07-24 9:43 ` Murat Kilivan
2014-07-24 10:08 ` Johan Hedberg
2014-07-24 10:47 ` Murat Kilivan
2014-07-24 15:12 ` David Herrmann
2014-07-24 15:32 ` Johan Hedberg
2014-07-28 8:38 ` Luiz Augusto von Dentz
2014-07-28 8:53 ` David Herrmann
2014-07-28 10:21 ` Luiz Augusto von Dentz
2014-07-28 12:39 ` <COMMERCIAL>: " Murat Kilivan
2014-07-28 15:15 ` David Herrmann
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=20140724083116.GB9891@t440s.lan \
--to=johan.hedberg@gmail.com \
--cc=Murat.Kilivan@csr.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox