This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Binary increased memory ( leaks )

From: Jim Wilson <wilson at tuliptree dot org>
To: "Klein, Bernhard" <Bernhard dot Klein at logicacmg dot com>
Cc: gcc-help at gcc dot gnu dot org, gcc at gcc dot gnu dot org
Date: Thu, 12 Jun 2003 16:18:47 -0700
Subject: Re: Binary increased memory ( leaks )
References: <0F232CC93A58D6119C1600B0D0799B810107E0F0@hamsrvmx03.logica.co.uk>

Klein, Bernhard wrote:

Now, I had the problem, that two of my binaries works properly, but if I
checked the memory with "top" I saw, that the memory usage continous
increased.

First figure out what kind of memory is being leaked. Stack? Malloc? mmap? You should be able to figure this out in gdb by checking the stack pointer value and the sbrk(0) value. If stack, then a gdb backtrace should be helpful. If malloc, a quick check of the FSF GNU project pages shows a pointer to a MemWatch program that might be helpful. http://www.gnu.org/directory/memwatch.html See also the list of related programs.

Jim

References:
- Binary increased memory ( leaks )
  - From: Klein, Bernhard

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]