This is the mail archive of the
mailing list for the Java project.
RE: GC latency in GCJ
- From: Andrew Haley <aph at redhat dot com>
- To: "Boehm, Hans" <hans dot boehm at hp dot com>
- Cc: "P.O. Gaillard" <pierre-olivier dot gaillard at fr dot thalesgroup dot com>, <java at gcc dot gnu dot org>
- Date: Tue, 25 Apr 2006 11:42:56 +0100
- Subject: RE: GC latency in GCJ
- References: <65953E8166311641A685BDF71D865826A76842@cacexc12.americas.cpqcorp.net>
Boehm, Hans writes:
> It used to be that if you built libgcj with --enable-gc-debug, the
> collector would write an abbreviated stack trace in each object,
> and you could use that for some low-tech heap profiling, etc. I
> believe that still works at the GC level, but I'm not sure the gcj
> infrastructure still works. I haven't tried it very recently.
I tried --enable-gc-debug recently, and it still works. I didn't try
backtrace, but I'm sure that works too.