anchor.diff:  
   Additional information on which classes are initialized and why can be obtained by passing in the `-H:+PrintClassInitialization` flag via `-Dquarkus.native.additional-build-args`.
   
  +[[profiling]]
   == Profile Runtime Behaviour
   
   === Single Thread
  
positive.code: so JFR is the only way to gather any information in this situation.
  As JFR support for native expands,
  the ability to detect root causes of performance issues directly in production will improve.
  
negative.code: When you open the flamegraph, you will see all threads' work collapsed into a single area.
  Then, you can clearly see that there's some locking that could affect performance.
  
  [[debug-info]]
  == Debugging Native Crashes
  
  One of the drawbacks of using native executables is that they cannot be debugged using the standard Java debuggers,
  