All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Bug in SDP example?
Date: Wed, 23 Jan 2008 00:07:03 -0200	[thread overview]
Message-ID: <4796A147.7090505@aircable.net> (raw)

Hello guys,
I've been tracing a bug in part of Tadas work (obex-data-server), and I
finally found it, it was related to sdp records calls, the dbus
interface specifies to use array of byte, while he was using array of
int. So I replaced
DBUS_TYPE_G_UINT_ARRAY for DBUS_TYPE_G_UCHAR_ARRAY, and valgrind stopped
blaming about bugs.

Strange is that the example at this page:
http://wiki.bluez.org/wiki/HOWTO/DiscoveringServices

Seems to have exactly the same problem in the D-Bus glib example. The
D-Bus function call that has an error is this one:
dbus_g_proxy_call (adapter_proxy,
"GetRemoteServiceRecord", &error,
G_TYPE_STRING, address,
G_TYPE_UINT, *((guint32 *)handle_array->data),
G_TYPE_INVALID,
DBUS_TYPE_G_UINT_ARRAY, &record_array,
G_TYPE_INVALID)

I'm not 100% sure, but I've been through both hcid and sdpd sources from
the latest bluez libs and seems like I'm right. It should say:
DBUS_TYPE_G_UCHAR_ARRAY, &record_array,
Instead of:
DBUS_TYPE_G_UINT_ARRAY, &record_array,

Any of the gurus out there can confirm this? I don't want to fix the
example if it's all ready all right.

Thanks,
Manuel Naranjo
Wireless Cables Inc. www.aircable.net


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-01-23  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23  2:07 Manuel Naranjo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-23  2:08 [Bluez-devel] Bug in SDP example? Manuel Naranjo

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=4796A147.7090505@aircable.net \
    --to=manuel@aircable.net \
    --cc=bluez-devel@lists.sourceforge.net \
    /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.