I ran into a nasty bug today.
Call OBEX_FreeInterfaces multiple times and it will try to free the
memory each time. That results in a "double free SEGV".
OBEX_FindInterfaces calls OBEX_FreeInterfaces to clear out old entries.
So if you free the struct returned from find when you are done with it
(like a good programmer will do) the next call to find will fail horribly.
Pointers to already freed memory are dangerous always.
With the patch OBEX_FreeInterfaces will set the pointer to NULL after
freeing the memory.
Both lacked parameter checking, too.
The patch is already applied to CVS.
Get latest updates about Open Source Projects, Conferences and News.