Hi Maxwell !
Le jeudi 4 mars 2010 16:26:45, Maxwell Rathbone a écrit : > Thanks for your reply, I appreciate you taking the time to try and help > me. Thank you for your patience as well :-) > While I do agree with you that a package repository would certainly > have made this a lot easier, I'm certainly up for solving dependencies. > As for simplifying the process, my biggest complaint is not knowing what > the dependencies are ahead of time. I'd just have to try and > configure/make over and over to find out that a package was missing, > install that and then try again. Just for curiosity... as redhat doesnt > seem to be, what is the preferred OS for liquidsoap? Most of us use Debian, but there are also packages maintained for Arch linux. There might be others but I do not remember it right now.. > Moving on.. > > I tried your recommendation of outputting to a file instead of the > SHOUTcast stream. I downloaded the mp3 to my local PC and played it and > the output was nearly flawless. So this does appear to indicate a > problem specifically with outputting to a SHOUTcast server. However, > when it went to start the next song in the playlist, it crashed due to > what appears to be a memory allocation error. Here is the output of what > I saw on the screen: (...) > "/home/liquidsoap/Summer Channel feat. Fisher - A Thousand Miles > (Burufunk Remix).mp3". > terminate called after throwing an instance of 'std::bad_alloc' > what(): St9bad_alloc > ./start.sh: line 2: 13082 Aborted (core dumped) Woops.. This is a pretty bad error and I have never seen it before... It's most probably coming from the C code, either the ocaml bindings (let's hope not..) or directly a C library outside of our codebase.. Also, judging from the name of the symbol, it seems to come from some C++ code, which narrows the possible culpritsa lot.. Let's hope it was temporary. If it appears again, it would be very useful to get a backtrace of the error using gdb. I won't detail how now, but we could help you. > I believe I am using the latest version of ocaml-cry, as I just > downloaded it a few days ago: > ocaml-cry-0.1.1 The latest ocaml-cry version is 0.1.2 and this is the one that fixes a possible issue with network communications.. > I'd be curious how I could try the ocaml-shout instead of ocaml-cry to > see if perhaps the newer ocaml-cry is causing this issue. That is a good idea. However, you would have to use liquidsoap 0.9.1 or less. 0.9.2 is only meant to be used with ocaml-cry... Let's hope that ocaml-cry 0.1.2 fixes your issue.. :-) Cheers, Romain ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
