Mercurial > hg > graal-compiler
comparison agent/doc/index.html @ 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 | a61af66fc99e |
| children |
comparison
equal
deleted
inserted
replaced
| 6965:3be318ecfae5 | 6972:bd7a7ce2e264 |
|---|---|
| 218 These scripts are used to run SA remotely. | 218 These scripts are used to run SA remotely. |
| 219 </td> | 219 </td> |
| 220 </tr> | 220 </tr> |
| 221 </table> | 221 </table> |
| 222 | 222 |
| 223 <h3>C2 Compilation Replay</h3> | |
| 224 <p> | |
| 225 When a java process crashes in compiled method, usually a core file is saved. | |
| 226 The C2 replay function can reproduce the compiling process in the core. | |
| 227 <a href="c2replay.html">c2replay.html</a> | |
| 228 | |
| 223 <h3>Debugging transported core dumps</h3> | 229 <h3>Debugging transported core dumps</h3> |
| 224 <p> | 230 <p> |
| 225 When a core dump is moved from the machine where it was produced to a | 231 When a core dump is moved from the machine where it was produced to a |
| 226 difference machine, it may not always be possible for SA to debug the same. | 232 difference machine, it may not always be possible for SA to debug the same. |
| 227 More info. on debugging on transported core dumps is in | 233 More info. on debugging on transported core dumps is in |