What's the purpose of the Hotspot flag, ForceFullGCJVMTIEpilogues
Daniel D. Daugherty
daniel.daugherty at oracle.com
Thu Dec 9 14:04:54 PST 2010
$ hg annotate src/share/vm/runtime/globals.hpp | grep
ForceFullGCJVMTIEpilogues
866: product(bool, ForceFullGCJVMTIEpilogues,
false, \
$ hg log -r 866 -v src/share/vm/runtime/globals.hpp
changeset: 866:2b4230d1e589
parent: 506:26bc4770e671
user: dcubed
date: Tue Jul 28 13:35:00 2009 -0600
files: src/share/vm/memory/genCollectedHeap.cpp
src/share/vm/prims/jvmtiExport.cpp src/share/vm/runtime/globals.hpp
description:
6862295: JDWP threadid changes during debugging session (leading to
ingored breakpoints)
Summary: Correctly count full GC operations for framework collectors.
Add ForceFullGCJVMTIEpilogues as a future work around if needed.
Reviewed-by: jcoomes, alanb, ysr
Dan
On 12/9/2010 2:49 PM, Keith McGuigan wrote:
>
> See subject. Does anybody know? The only thing it appears to do is
> cause a recaching of the JvmtiBreakpoint cache after minor
> collections, which is unnecessary as a minor collection will not
> change any bytecode pointers. It's a "product" flag, defaulting to
> false. Can it be removed or deprecated? It seems useless.
>
> --
> - Keith
More information about the serviceability-dev
mailing list