Icecast - Jan 2012 - ices2 memory leak on Debian/ARM (The Darkener)

Hi Keith,

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!

- Jordan

On 01/10/2012 07:43 AM, Keith Roberts wrote:
> *snip*
> 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
>
> -----------------------------------------------------------
> Websites:
> http://www.karsites.net
> http://www.php-debuggers.net
> http://www.raised-from-the-dead.org.uk
>
> All email addresses are challenge-response protected with
> TMDA [http://tmda.net]
> -----------------------------------------------------------
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Jordan (PGP: 0xDA470FF8)

Can you describe your architecture?
-- 
Christian Eichert

_____________________________________________
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)


Hi Keith,

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!

- Jordan

On 01/10/2012 07:43 AM, Keith Roberts wrote:
> *snip*
> 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
>
>_____________________________________________
> Websites:
> http://www.karsites.net
> http://www.php-debuggers.net
> http://www.raised-from-the-dead.org.uk
>
> All email addresses are challenge-response protected with
> TMDA [http://tmda.net]
>_____________________________________________
>_____________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-- 
Jordan (PGP: 0xDA470FF8)

_____________________________________________

Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.xiph.org/pipermail/icecast/attachments/20120110/587e1f68/attachment.htm

ARM, default install on an Ionics Stratus plug computer -
http://www.ionicsplug.com/stratus.html ) - running Current Debian Stable.

- Jordan


On 01/10/2012 03:13 PM, Christian Eichert [K9] wrote:
> Can you describe your architecture?
> -- 
> Christian Eichert
>
> ------------------------------------------------------------------------
> *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)
>
> Hi Keith,
>
> 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!
>
> - Jordan
>
> On 01/10/2012 07:43 AM, Keith Roberts wrote:
> > *snip*
> > 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 proble
>  ms,
> 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
> >
> >
> ------------------------------------------------------------------------
>
> > Websites:
> > http://www.karsites.net
> > http://www.php-debuggers.net
> > http://www.raised-from-the-dead.org.uk
> >
> > All email addresses are challenge-response protected with
> > TMDA [http://tmda.net]
> >
> ------------------------------------------------------------------------
>
> >
> ------------------------------------------------------------------------
>
> > 
>  Icecast
> mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
>
>
> -- 
> Jordan (PGP: 0xDA470FF8)
>
> ------------------------------------------------------------------------
>
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>

-- 
Jordan (PGP: 0xDA470FF8)

On Tue, 10 Jan 2012, TheDarkener wrote:
> 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!
If it is a memory leak because of some bug in the source code, using 
Valgrind on one of its supported platforms would probably be a smart thing 
to do. Fix the source code and recompile on any other platform, and the 
bug should be gone ;-)

Admittedly, x86 and amd64 may not have the exact same issues, e.g. 
data-alignment may be different, but memory leaks should still be memory 
leaks.

Just my 2 cents..

-- 
Maarten