Le samedi 12 septembre 2009 23:26:30, polemon a écrit :
> > If everything goes well, we should have a backtrace of the exception
> > that  should help to find out were it was raised.
> 
> As I remember correctly, I compiled with --enable-debugging, however, I did
>  not run it in a console. For this, I'll try running it in a screen
>  session. we'll see what this gives us...

Ok

> > Now, the random nature of the bug seems to indicate that it is not
> > necessarly  deterministic. That makes it harder to find out. The obvious
> > things to check at first glance would be whether there is no socket/file
> > descriptor leak. This can be done by:
> >   lsof | grep <pid-of-liquidsoap>
> > Where you replace <pid-of-liquidsoap> by the pid of the running
> > liquidsoap. 
> 
> OK, just did that:

Ok. Keep an eye on it to see if it is not growing indefinitely..


Romain

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to