anchor.diff:  Since we're dealing with a linux native executable,
   we can use tools like `perf` directly.
   To use `perf`,
  -start the tools container created earlier as a privileged user:
  -
  -[source,bash]
  -----
  -cd debugging-native
  +go to the root of the project and start the tools container created earlier as a privileged user:
  +
  +[source,bash]
  +----
   docker run --privileged -t -i --rm -v ${PWD}:/data -p 8080:8080 fedora-tools:v1
   ----
   
  
positive.code: The omitted output above contains clues to what caused the issue,
  but in this exercise we are going to assume that no information was provided.
  Let’s try to debug the segmentation fault using `gdb`.
  To do that, first enter the tools container:
  
  [source,bash]
  ----
  cd debugging-native
  docker run -t -i --rm -v ${PWD}:/data -p 8080:8080 fedora-tools:v1 /bin/bash
  ----
  
  
negative.code: curl -w '\n' http://localhost:8080/hello
  ----
  
  The rest of this section explores ways to build the native executable with extra information,
  but first, stop the running application.
  We can obtain this information while building the native executable by adding additional native-image build options using `-Dquarkus.native.additional-build-args`, e.g.
  
  [source,bash,subs=attributes+]
  ----
  