public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Sattler <post@hendrik-sattler.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SDP services cannot be unregistered
Date: Thu, 20 Dec 2007 22:40:33 +0100	[thread overview]
Message-ID: <200712202240.34586.post@hendrik-sattler.de> (raw)
In-Reply-To: <1198116580.8050.232.camel@aeonflux>

Am Donnerstag 20 Dezember 2007 schrieben Sie:
> first of all you are using the unregister function wrongly. You have to
> give it the exact record structure you gave the register function. So
> when you allocate a new record, then the unregister has no idea what to
> do with it.

Ok, I remember now everything related to the record and it works. One note 
though: the sdp_record_free() function always crashes. Is it actually 
supposed to be used? Or asked the other way: how is one supposed to free the 
previously allocated stuff correctly? Or is this done automatically?

> Why it doesn't cleanup after program termination is unclear to me. That
> should actually work. You might wanna investigate on that one.

I will try that, although I took the way of catching SIGINT and SIGTERM, now.

Thanks for your help.

HS

  parent reply	other threads:[~2007-12-20 21:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 22:41 [Bluez-devel] SDP services cannot be unregistered Hendrik Sattler
2007-12-19 23:34 ` Marcel Holtmann
     [not found]   ` <200712200229.40589.post@hendrik-sattler.de>
2007-12-20  2:09     ` Marcel Holtmann
2007-12-20  9:20       ` Hendrik Sattler
2007-12-20 15:08         ` Marcel Holtmann
2007-12-20 21:40       ` Hendrik Sattler [this message]
2007-12-20 23:12         ` Marcel Holtmann
2007-12-20  9:59   ` [Bluez-devel] Multi-device : maximizing the number of concurrent ourgoing RFCOMM connections Olivier Le Pogam

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=200712202240.34586.post@hendrik-sattler.de \
    --to=post@hendrik-sattler.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.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