public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlo Giuseppe Monaco <carlogmonaco@hotmail.it>
To: <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] adding PDU and debbugging sdp daemon
Date: Thu, 26 Jun 2008 15:27:18 +0200	[thread overview]
Message-ID: <BLU120-W31892B117FCE752B773847A6A30@phx.gbl> (raw)
In-Reply-To: <BLU120-W31FBA90BA2C2FBD7924E54A6A30@phx.gbl>


[-- Attachment #1.1: Type: text/plain, Size: 1271 bytes --]








 


Dear Sir,

I'm modifying bluez-libs and bluez-utils (i'm using
3.9 version) to introduce new pdu relating to registration, request and
response of new services.
For example  i'm adding new pdu types, defining them into  bluez-libs-3.9/include/sdp.h 

# define SDP_NEW_REGISTER_REQ 0x85

But
during debugging I returned errno = EINVAL (set by sdp_device_record_register_binary written in sdp.c ) and the sdp daemon log file 
gets the following result: 

Jun 25 21:26:31 pinta-desktop hcid[4967]: Unknown PDU ID : 0x85 received 
(i thintk it's a message sent from function process_request
written in bluez_utils_3.9/sdpd/request.c )
 
How can i accept new types of pdu declared?
Is
there a way to debug sdp daemon alternative to log file, for example
using gdb o using particular options in ./configure command? I tried
using --enable-debug option for configure and launching gdb, but they
don't work.


Thanks for your support and sorry for my english.

Best Regards,
Carlo M. 

_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us

[-- Attachment #1.2: Type: text/html, Size: 2101 bytes --]

[-- Attachment #2: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-06-26 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  6:03 [Bluez-users] Sbc encode optimization salyer
2008-06-26 13:22 ` [Bluez-devel] adding PDU and debbugging sdp daemon Carlo Giuseppe Monaco
2008-06-26 13:27   ` Carlo Giuseppe Monaco [this message]
2008-06-26 14:26 ` [Bluez-users] Sbc encode optimization Brad Midgley

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=BLU120-W31892B117FCE752B773847A6A30@phx.gbl \
    --to=carlogmonaco@hotmail.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox