[Icecast] ices2 memory leak on Debian/ARM (The Darkener)
Christian Eichert [K9]
email at christianeichert.de
Tue Jan 10 15:20:32 PST 2012
Can you describe your architecture?
Von: TheDarkener <thedarkener at logicalnetworking.net>
Gesendet: Wed Jan 11 00:02:01 MEZ 2012
An: icecast at xiph.org
Betreff: Re: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
As I explained before, Valgrind won't run in my arch. I'll Google for
some other memory leak detection tools, however. Thank you for your
input...I look forward to helping fix this bug!
On 01/10/2012 07:43 AM, Keith Roberts wrote:
> There's a Linux memory profiler called:
> "Valgrind" is a multipurpose code profiling and memory
> debugging tool for Linux when on the x86 and, as of version
> 3, AMD64, architectures. It allows you to run your program
> in Valgrind's own environment that monitors memory usage
> such as calls to malloc and free (or new and delete in C++).
> If you use uninitialized memory, write off the end of an
> array, or forget to free a pointer, Valgrind can detect it.
> Since these are particularly common problems, this tutorial
> will focus mainly on using Valgrind to find these types of
> simple memory problems, though Valgrind is a tool that can
> do a lot more.
> that might help you out. I've used it to find programs
> running under Linux with bad memory management.
> For other memory leakage tools, just Google for something
> like: memory leak detection tools
> Kind Regards,
> Keith Roberts
> All email addresses are challenge-response protected with
> TMDA [http://tmda.net]
> Icecast mailing list
> Icecast at xiph.org
Jordan (PGP: 0xDA470FF8)
Icecast mailing list
Icecast at xiph.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Icecast