public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] SDP lib memory leak
Date: Fri, 31 Aug 2007 20:45:20 +0200	[thread overview]
Message-ID: <1188585920.13373.105.camel@violet> (raw)
In-Reply-To: <46D84FBD.60203@gmail.com>

Hi Manuel,

> I have made an application that makes use of the sdp lib. By 
> running the app with valgrind [1] I found a memory leak.
> There's an static variable called bluetooth_base_uuid that's being 
> initializated once but then never freed.
> I had added a method that should be called, only when the thread is 
> about to end that frees that variable.
> Attached you can see the patch.

thanks for the patch, but I put a different patch in the CVS that avoids
any memory allocation at all.

Can you extract me a test program from your application, so I can double
check that it is doing the right thing on little and big endian systems
and we don't have any memory leaks at all anymore.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-08-31 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 17:28 [Bluez-devel] [PATCH] SDP lib memory leak Manuel Naranjo
2007-08-31 18:45 ` Marcel Holtmann [this message]
2007-08-31 19:11   ` 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=1188585920.13373.105.camel@violet \
    --to=marcel@holtmann.org \
    --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