Icecast dev - Oct 2004 - Icecast 2.0.1 segmentation fault under LInux

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.
Just to clarify my understanding, this would be something caused by code in 
Icecast or one of its dependent libs, not some other running process, 
right?  And whatever is doing this would only be corrupting Icecast memory 
and nothing accessed by any other app?  Or not?

Geoff.

On Wednesday 06 October 2004 13:56, Geoff Shang wrote:
> 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.
>
> Just to clarify my understanding, this would be something caused by code in
> Icecast or one of its dependent libs, not some other running process,
> right?  And whatever is doing this would only be corrupting Icecast memory
> and nothing accessed by any other app?  Or not?
>
That's correct: icecast is doing something bad internally, and corrupting
its
own datastructures. It can't cause problems for other applications (well, 
unless those applications are relying on icecast working correctly!).

Mike

Hi:

Just to let everyone know that I upgraded to Icecast 2.0.2 and its run 
solidly for days.  Go figure.

Geoff.