anchor.diff:  Debugging Quarkus native executables experience is best done within a Linux environment.
   Root access is not needed except to install packages required to run some debug steps,
   or to enable `perf` to gather events at the kernel.
  -Debugging in MacOS and Windows environments also works in a container environment (see <<macwindows,FAQ entry>>).
  +Debugging in macOS and Windows environments also works in a container environment (see <<macwindows,FAQ entry>>).
   
   These are the packages you'll need on your Linux environment to run through the different debugging sections:
   
  
positive.code: This is because it has no idea what constitutes a root pointer nor how to recursively trace pointers from those roots.
  
  [[macwindows]]
  === Can I follow these examples if I’m running MacOS or Windows?
  
  The ideal environment for trying out these debugging examples is Linux.
  All examples, except for profiling and debugging native crashes, can also be executed natively in either MacOS or Windows.
  If you are in either of these two platforms, you can run all the steps (including native crash debugging and profiling) within a Linux container.
  The following `Dockerfile` shows what a Linux container requires in order to follow the examples:
  
  
negative.code: Aside from system level packages, you'll need:
  
  * JDK 11 installed with `JAVA_HOME` configured appropriately
  * Apache Maven {maven-version}
  * A working container runtime (Docker, podman)
  * The code of the application developed in the xref:getting-started.adoc[Getting Started Guide].
  
  