All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Crane <steve.crane@rococosoft.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Stefan Mischke <StefanMischke@web.de>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
	"Stefan Mischke (E-Mail)" <survivor@upb.de>
Subject: Re: [Bluez-devel] SDP memory leak?
Date: Fri, 27 Aug 2004 15:40:35 +0100	[thread overview]
Message-ID: <1093617635.5848.53.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <1093613681.2581.135.camel@pegasus>

Hi Marcel, Stefan,

On Fri, 2004-08-27 at 14:34, Marcel Holtmann wrote:
> Hi Steve,
> 
> > The sdp library is free (I think) of memory leaks, thanks to the wonders
> > of valgrind: http://valgrind.kde.org.
> 
> would you also take care of the tools in bluez-utils that uses the SDP
> library?

I have just committed changes to pand's service registration. The CVS
diff should show what is required to fix this in the other applications.
(Note: sdptool also cleans up properly in its "add" subcommands.)

Unfortunately I haven't time to do the others at the moment but this
should be a start for others. (Send in the patches!)

Regards,
Steve
-- 
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)

  reply	other threads:[~2004-08-27 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 12:32 [Bluez-devel] SDP memory leak? Stefan Mischke
2004-08-27 12:49 ` Marcel Holtmann
2004-08-27 13:24   ` Stefan Mischke
2004-08-27 13:28     ` Marcel Holtmann
2004-08-27 13:31   ` Stephen Crane
2004-08-27 13:34     ` Marcel Holtmann
2004-08-27 14:40       ` Stephen Crane [this message]
2004-08-27 17:26         ` Marcel Holtmann

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=1093617635.5848.53.camel@baroque.rococosoft.com \
    --to=steve.crane@rococosoft.com \
    --cc=StefanMischke@web.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=survivor@upb.de \
    /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.