Ensure AOT compilation in jitdump

[dsouzai]

If a crash happens in an AOT body, the jitdump should generate an AOT compilation. However, this is not as trivial as it might seem, as there are three scenarios:

• 1. Crash during an AOT compile - Ensure AOT Compilation in JIT Dump #10852
• 2. Crash in an AOT body that was generated in the current JVM instance
• 3. Crash in an AOT body that was generated in a different JVM instance

Regarding 2, should the jitdump redo the AOT compilation, the AOT load, or both?
Regarding 3, should the jitdump redo the AOT load?

---

[dsouzai]

fyi @mpirvu @fjeremic

[mpirvu]

I wonder about the value of [3] since typically we want to get to compilation logs.
Moreover, the advantage of jitdump is that it can generate a log from the the same JDK that produced the bad jitted body. If the AOT body has been produced in a previous run, we lose that advantage, so a compilation log from a brand new JVM invocation may be just as good.

Regarding 2, should the jitdump redo the AOT compilation, the AOT load, or both?

I think we want to redo the AOT compilation.

[dsouzai]

^T'was by accident