From: soraberri <421246@posta.unizar.es>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: baswap neccesity
Date: Tue, 11 Jan 2005 09:52:07 +0100 [thread overview]
Message-ID: <cs044v$o6q$1@sea.gmane.org> (raw)
In-Reply-To: <1105388822.8652.53.camel@pegasus>
Hello Marcel,
Marcel Holtmann wrote:
> Hi,
>
>
>>I'm reading rctest.c:
>>In do_connect function, a call to bswap is used just before the connect
>>call:
>> baswap(&rem_addr.rc_bdaddr, strtoba(svr));
>>
>>In the server, baswap is again called just after the accept call
>>
>>Why is it neccesary? Why does the server listening at the other side
>>expect addresses in such byte ordering?
>
>
> this is part of the specification. The textual representation and the
> over-air BD_ADDR is swapped.
>
> However the code above has a memory leak. Where do you found it?
this piece of code is from the 'bluez-utils-2.13.tar.gz' package which
is downloadable now at the web site. Precisely in function 'int
do_connect(char *svr)' of rctest.c.
It's curious, I'm sure you'd see memory leaks where I only see flowers!
thanks Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-11 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 18:36 [Bluez-devel] baswap neccesity soraberri
2005-01-10 18:47 ` [SPAM?]: " Till Harbaum
2005-01-10 20:27 ` Marcel Holtmann
2005-01-11 8:52 ` soraberri [this message]
2005-01-11 9:59 ` [Bluez-devel] " 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='cs044v$o6q$1@sea.gmane.org' \
--to=421246@posta.unizar.es \
--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