Fri, 20 Sep 2013 10:53:28 +0200
8024974: Incorrect use of GC_locker::is_active()
Summary: SymbolTable and StringTable can make calls to GC_locker::is_active() outside a safepoint. This isn't safe because the GC_locker active state (lock count) is only updated at a safepoint and only remains valid as long as _needs_gc is true. However, outside a safepoint_needs_gc can change to false at any time, which makes it impossible to do a correct call to is_active() in that context. In this case these calls can just be removed since the input argument to basic_add() should never be on the heap and so there's no need to check the GC_locker state. This change also adjusts the assert() in is_active() to makes sure all calls to this function are always done under a safepoint.
Reviewed-by: brutisso, dcubed
Contributed-by: per.liden@oracle.com
duke@435 | 1 | -export:JNI_GetDefaultJavaVMInitArgs |
duke@435 | 2 | -export:JNI_CreateJavaVM |
duke@435 | 3 | -export:JNI_GetCreatedJavaVMs |
duke@435 | 4 | |
duke@435 | 5 | -export:jio_snprintf |
duke@435 | 6 | -export:jio_printf |
duke@435 | 7 | -export:jio_fprintf |
duke@435 | 8 | -export:jio_vfprintf |
duke@435 | 9 | -export:jio_vsnprintf |
duke@435 | 10 |