comparison src/share/vm/ci/ciInstanceKlass.hpp @ 6972:bd7a7ce2e264

6830717: replay of compilations would help with debugging Summary: When java process crashed in compiler thread, repeat the compilation process will help finding root cause. This is done with using SA dump application class data and replay data from core dump, then use debug version of jvm to recompile the problematic java method. Reviewed-by: kvn, twisti, sspitsyn Contributed-by: yumin.qi@oracle.com
author minqi
date Mon, 12 Nov 2012 14:03:53 -0800
parents da91efe96a93
children 2cb439954abf 6f3fd5150b67
comparison
equal deleted inserted replaced
6965:3be318ecfae5 6972:bd7a7ce2e264
228 bool is_in_package(const char* packagename, int len); 228 bool is_in_package(const char* packagename, int len);
229 229
230 // What kind of ciObject is this? 230 // What kind of ciObject is this?
231 bool is_instance_klass() const { return true; } 231 bool is_instance_klass() const { return true; }
232 bool is_java_klass() const { return true; } 232 bool is_java_klass() const { return true; }
233
234 // Dump the current state of this klass for compilation replay.
235 virtual void dump_replay_data(outputStream* out);
233 }; 236 };
234 237
235 #endif // SHARE_VM_CI_CIINSTANCEKLASS_HPP 238 #endif // SHARE_VM_CI_CIINSTANCEKLASS_HPP