public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Broken SDP parsing?
Date: Mon, 9 Mar 2009 11:53:10 -0300	[thread overview]
Message-ID: <2d5a2c100903090753s3e192df3uc62473a45c8efae4@mail.gmail.com> (raw)
In-Reply-To: <2d5a2c100903090732x6d677dccp747c469b43906f71@mail.gmail.com>

Hi,

On Mon, Mar 9, 2009 at 11:32 AM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> Hi Bastien,
>
> On Mon, Mar 9, 2009 at 11:14 AM, Bastien Nocera <hadess@hadess.net> wrote:
>> Both use the code in common/sdp-xml.[ch] and convert_sdp_record_to_xml()
>> in particular, which is why it makes no sense to me...
>>
>> I double-checked by adding some debug to convert_raw_data_to_xml() and
>> the string for the attribute I'm interested in is empty, so it must be a
>> problem parsing the raw data from the device, or there's something that
>> strips this value somewhere in bluetoothd...
>
> Then I fear that my code of dumping an sdp record (sdp_copy_record) is
> probably not copying the string correctly.

That is exactly what is causing the problem, sdp_copy_record detects
the size of string with strlen (libs/sdp.c:511), which probably will
return 0 as the string seems to start with \0, so we probably need
some special handling for this.

Btw, this is not really a problem of sdp_copy_record but
sdp_data_alloc, so there a high chance that we may fix other bugs
related to this.

-- 
Luiz Augusto von Dentz
Engenheiro de Computação

  reply	other threads:[~2009-03-09 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  1:00 Broken SDP parsing? Bastien Nocera
2009-03-08 14:46 ` Bastien Nocera
2009-03-09 13:08   ` Luiz Augusto von Dentz
2009-03-09 14:14     ` Bastien Nocera
2009-03-09 14:32       ` Luiz Augusto von Dentz
2009-03-09 14:53         ` Luiz Augusto von Dentz [this message]
2009-03-09 15:25         ` Bastien Nocera
2009-03-09 16:40           ` Luiz Augusto von Dentz
2009-03-09 17:09             ` Bastien Nocera
2009-03-09 18:04               ` Johan Hedberg
2009-03-09 19:29                 ` Port CUPS discovery to BlueZ 4.x (Re: Broken SDP parsing?) Bastien Nocera
2009-03-13 15:37                 ` Broken SDP parsing? Bastien Nocera
2009-03-13 18:15                   ` Johan Hedberg
2009-03-14  0:39                     ` Bastien Nocera
2009-03-14 13:29                       ` Johan Hedberg

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=2d5a2c100903090753s3e192df3uc62473a45c8efae4@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=hadess@hadess.net \
    --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