From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Mischke <StefanMischke@web.de>
Cc: 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 14:49:29 +0200 [thread overview]
Message-ID: <1093610969.2581.119.camel@pegasus> (raw)
In-Reply-To: <412F29D2.7000001@web.de>
Hi Stefan,
> I have a question about "bnep_sdp_search()" from
> "bluez-pan-1.1/pand/sdp.c" (see below for the code).
> If I see it correctly, the memory for "sdp_list_t *srch, *rsp" is
> allocated by "sdp_service_search_req()".
> But "bnep_sdp_search()" accesses the pointer "rsp" after it has done
> "sdp_close()".
> So my question is: 'Who will ever free the memory allocated at "rsp" and
> when?'
>
> I quite new to this, so I probably have missed something. So sorry if
> this is a stupid one :-).
no, I think you are right. I expect more memory leaks in the SDP code.
We need some people to check this and send me patches.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-27 12:49 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 [this message]
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
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=1093610969.2581.119.camel@pegasus \
--to=marcel@holtmann.org \
--cc=StefanMischke@web.de \
--cc=bluez-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox