RFR: JDK-8253001: [JVMCI] Add API for getting stacktraces independently of current thread

[Allan Gregersen]

On Thu, 24 Sep 2020 11:16:17 GMT, Erik Österlund <eosterlund at openjdk.org> wrote:

>The problem you describe is what _jvmti_can_access_local_variables capability is for. A debugger will have this set,
>and hence while debugging, we just don't scalarize stuff, so all objects are simply materialized. JVMCI already exposes
>this variable and presumably plays by the same rules.

A few questions pops into my mind:

1. What is the performance implications on setting _jvmti_can_access_local_variables capability? More specifically,
does this capability kill off escape analysis for a GraalVM?

2. When we have multiple Truffle contexts running, including but not limited to different guest languages, can we make
sure that escape analysis is only switched off on very specific parts of the host system with this set and can we
enable/disable this capability on the fly?

-------------

PR: https://git.openjdk.java.net/jdk/pull/110