This is the mail archive of the java@gcc.gnu.org mailing list for the Java 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: Detecting memory leaks

From: Bryce McKinlay <mckinlay at redhat dot com>
To: Jari Korva <jpkorva at iki dot fi>
Cc: java at gcc dot gnu dot org
Date: Mon, 27 Sep 2004 11:49:02 -0400
Subject: Re: Detecting memory leaks
References: <Pine.GSO.4.58.0409221325210.8763@paju.oulu.fi> <Pine.GHP.4.58.0409222047090.19740@tomil.hpl.hp.com> <Pine.GSO.4.58.0409231043070.4425@paju.oulu.fi>

Jari Korva wrote:

Thanks for the hint! If I understand correctly, it is C, not GC:

...

Are there any tools that can help me from there? I know that in general there are many tools, but are they applicable to gcj and ARM (it seems that I'm too lazy to try them myself ;) ?

Unfortunately I don't know of a tool which can easily help diagnose leaks in the native parts of libgcj. valgrind doesn't yet run libgcj, unfortunately - I believe this is because its emulation of POSIX signals is inadequate.

There are some known leaks in our AWT implementation, for example, (see http://gcc.gnu.org/PR16722) so a working leak detector would be very nice to help track these down.

Regards

Bryce

References:
- Detecting memory leaks
  - From: Jari Korva
- Re: Detecting memory leaks
  - From: Hans Boehm
- Re: Detecting memory leaks
  - From: Jari Korva

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