[Icecast-dev] Icecast 2.0.1 segmentation fault under LInux

[Geoff Shang]

Michael Smith wrote:

> This looks like something that should be "impossible". It's almost certainly
> memory corruption somewhere - and so the bug is probably somewhere else
> entirely, nowhere near this code.

Oh great. :)

> Do you have any way to reproduce this on demand? Or is it just something that
> happens apparently randomly?

Well I don't know.  I'd not had any problems at all until the last couple 
of weeks.  The server has crashed each day for the past few days.  This is 
the first time I've run it under GDB though.  I don't know if it's random 
or not, since there's no useful info in the logs that I can see (I've kept 
the logs though).  I can tell you that the last two times the server was p 
for the same amount of time (approximately), around 18.5 hours.

It's running against libogg 1.1 and libvorbis 1.0.1, if this helps.  Oh and 
curl 7.10.1.

> Upgrading to 2.0.2 is a good idea - I can't guarantee it'll help, but it's
> definately worth a try.

Should I upgrade to libogg 1.1.2 and vorbis 1.1 as well?

> If it doesn't help, any more information on how to reproduce this would be
> really helpful. If running it under valgrind is possible (i.e. you're running
> linux on x86, and you have some cpu to spare), that might be worthwhile too.

CPU is running pretty close to the mark up there, load average is usually 
over 2, since we run 6 streams up there plus the two vorbis ones running on 
the icecast server, and we have 4 LAME processes running as well as the two 
streamtranscoder processes which run these streams.  But it is running on 
x86 Linux.

So am I right in thinking that we can't glean anything more from this GDB 
session?  I'd really like to restart the server as soon as this is 
possible.

Geoff.