anchor.diff:  From there, you can either inspect the executable directly or use a tools container like above.
   ====
   
  +[[native-reports]]
   == Native Reports
   
   Optionally, the native build process can generate reports that show what goes into the binary:
  
positive.code: 
  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`.
  
  == Profile Runtime Behaviour
  
  === Single Thread
  
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,
  