Re: [Linphone-developers] Problem with Linphone 3.1.2 on Blackfin BF536

[Simon Morlat]

I agree. Indeed these are the symptoms of a leak of file descriptors. 
However my understanding is that the 1024 limit is per-process, so the leak 
would be within linphone or one its dependency, or the program that runs 
liblinphone if not linphonec.

First thing to do is to check your own code (if you use liblinphone directly 
or patched linphonec) for missing close() statements on opened file descriptors 
or sockets.
Then try to instrument the code by overriding every function that returns file 
descriptors (open, socket, pipe, socketpair...) and print a backtrace, do the 
same thing for close(), and try to find the one that gets leaked after the end 
of each call. Quite difficult unless there exist some specialised library or 
glibc debugging option to do that... Ask google.

Simon


Le vendredi 26 juin 2009 20:34:39, Nick Briggs a écrit :
> I'd suspect that some code is leaking file descriptors, and is hitting
> the default limit of 1024 open FDs -- i'd look at all the processes
> (sudo lsof) when it is in this broken state for some process that has an
> excessive number of FDs.   It likely one of the audio related processes
> that is being provoked by something Linphone is doing, rather than
> Linphone itself.
>
> Nick Briggs
> Palo Alto Research Center
>
>
> _______________________________________________
> Linphone-developers mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/linphone-developers