anchor.diff:  Then, you can clearly see that there's some locking that could affect performance.
   
   [[debug-info]]
  -== Debugging Native Crashes
  +=== Debugging Native Crashes
   
   One of the drawbacks of using native executables is that they cannot be debugged using the standard Java debuggers,
   instead we need to debug them using `gdb`, the GNU Project debugger.
  
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`.
  
  [[profiling]]
  == Profile Runtime Behaviour
  
  === Single Thread
  
  In this exercise, we profile the runtime behaviour of some Quarkus application that was compiled to a native executable to determine where the bottleneck is.
  Assume that you’re in a scenario where profiling the pure Java version is not possible, maybe because the issue only occurs with the native version of the application.
  
negative.code: 
  image::native-reference-perf-flamegraph-symbols.svg[Perf flamegraph with symbols]
  
  ==== Multi-Thread
  
  Multithreaded programs might require special attention when trying to understand their runtime behaviour.
  To demonstrate this, add this `MulticastResource` code to your project
  