From: "Claudio Takahasi" <claudio.takahasi@openbossa.org>
To: "Bastien Nocera" <hadess@hadess.net>
Cc: "Luiz Augusto von Dentz" <luiz.dentz@gmail.com>,
"Johan Hedberg" <johan.hedberg@gmail.com>,
"BlueZ development" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Fix possible crash on startup
Date: Tue, 14 Oct 2008 15:47:29 -0300 [thread overview]
Message-ID: <f9d4bd30810141147o60a2b0ban3773a949b5c6c236@mail.gmail.com> (raw)
In-Reply-To: <1223907411.31961.3251.camel@cookie.hadess.net>
2008/10/13 Bastien Nocera <hadess@hadess.net>:
> On Mon, 2008-10-13 at 10:43 -0300, Luiz Augusto von Dentz wrote:
>> Hi,
>>
>> I guess we can make all driver to do the discover on Connect if the
>> record is not available, similar to what is done in audio.
>
> I'm not certain whether the problem is no record, or a broken one.
>
> This is the file causing problems, the device line that causes the crash
> is the one starting with 00:1E:45:AD:F1:96. So there is data, but it
> probably isn't parsed properly.
>
> Cheers
>
Hi,
The source of this problem is an invalid sequence in the service
record. See entry 00:1E:45:AD:F1:96#02008007 in sdp record file.
About the Johan's questions:
1. we can access rec->handle directly, we have to fix it
2. service record is necessary, at least HIDDescriptorList
Claudio
--
--
Claudio Takahasi
Instituto Nokia de Tecnologia
Recife - Pernambuco - Brasil
+55 81 30879999
next prev parent reply other threads:[~2008-10-14 18:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 23:03 [PATCH] Fix possible crash on startup Bastien Nocera
2008-10-12 18:15 ` Johan Hedberg
2008-10-13 13:43 ` Luiz Augusto von Dentz
2008-10-13 14:16 ` Bastien Nocera
2008-10-14 18:47 ` Claudio Takahasi [this message]
2008-10-14 21:44 ` Claudio Takahasi
2008-10-14 22:51 ` Bastien Nocera
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=f9d4bd30810141147o60a2b0ban3773a949b5c6c236@mail.gmail.com \
--to=claudio.takahasi@openbossa.org \
--cc=hadess@hadess.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox