Re: [Bluez-users] malloc & free

[Marcel Holtmann <marcel@holtmann.org>]

Hi Pedro,

> In the application I am developing, I want to log some information about 
> Bluetooth devices, pretty much like "sdptool browse" and "hcitool info" 
> do. In the code of these applications, there are calls to some library 
> functions like hci_dflagstostr(), hci_lmtostr()... that create a string 
> with information about the device (flags, features, etc.).
> 
> The problem with these functions is that they call malloc(), expecting 
> the caller to call free(). The problem with that is that this approach 
> is not save, as it is not guaranteed that calling malloc() in a library 
> function and free() in the main program works. In fact, I have seen a 
> segmentation fault doing that.

explain why this is not safe.

> AFAIK, there are two alternatives: either the library functions expect a 
> buffer (and its size) to be filled or malloc() and free() are both done 
> within the library, which means creating a new library function call for 
> freeing buffers allocated with malloc(). Are any of this alternatives 
> implemented or on the roadmap? What workaround do you suggest?

We can do that, but it is not on my roadmap. Send my patches for it and
I will review them.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users