From: Pedro Monjo Florit <pedro.monjo@futurlink.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] sdptool
Date: Wed, 04 May 2005 18:05:16 +0200 [thread overview]
Message-ID: <4278F2BC.4080104@futurlink.com> (raw)
Hi!
I am following the code of sdptool.c and I have a question. I am
comparing add_sp() and add_opush() and I have found something that
puzzles me. The first part of the code is almost the same, but there are
some sdp_list_free() calls in add_opush() that are present in add_sp().
For example:
static int add_sp(sdp_session_t *session, svc_info_t *si)
{
/* ... */
sdp_uuid16_create(&sp_uuid, SERIAL_PORT_SVCLASS_ID);
svclass_id = sdp_list_append(0, &sp_uuid);
sdp_set_service_classes(&record, svclass_id);
sdp_list_free(svclass_id, 0);
/* ... */
}
static int add_opush(sdp_session_t *session, svc_info_t *si)
{
/* ... */
sdp_uuid16_create(&opush_uuid, OBEX_OBJPUSH_SVCLASS_ID);
svclass_id = sdp_list_append(0, &opush_uuid);
sdp_set_service_classes(&record, svclass_id);
/* ... */
}
Is this correct? Shouldn't there be a call to sdp_list_free(svclass_id,
0) in add_opush() too? As I understand it, this means that add_opush()
has a memory leak, isn't it? I have found at least three missing calls
to sdp_list_free() in add_opush().
Regards,
Pedro Monjo
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-05-04 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 16:05 Pedro Monjo Florit [this message]
2005-05-04 17:03 ` [Bluez-users] sdptool Stephen Crane
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=4278F2BC.4080104@futurlink.com \
--to=pedro.monjo@futurlink.com \
--cc=bluez-users@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