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 15:28:36 +0200 [thread overview]
Message-ID: <1093613316.2581.133.camel@pegasus> (raw)
In-Reply-To: <412F3619.40202@web.de>
Hi Stefan,
> Well then, I just figured out (in my own TestApp based on
> "bnep_sdp_search()") that it simply doesn't work like this. I propose to
> do "sdp_close()" as the last sdp_* call (as in the code below). Same
> with dund. So there might be no memory leak but an illegal pointer
> access. One has to correct "pand/sdp.c" and "dund/sdp.c".
I am very busy with some other problems and I am not the expert when it
comes to the SDP code. Write a patch that I can apply and show me that
it is the right way to do it. Be careful with the other return pathes in
that functions.
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 13:28 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 [this message]
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=1093613316.2581.133.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