title_body: How do I build a debug configuration of a Plutus project? When I try to set a breakpoint in a small Plutus project such as this, I always get the following error:
  :b Week05.Homework1.mkPolicy
  cannot set breakpoint on Week05.Homework1.mkPolicy: module Week05.Homework1 is not interpreted
  
  (Using Windows, cabal version 3.4.0.0, ghc version 8.10.4.)
  Removing -fobject-code or adding -fPIC to the ghc-options won't help, which was suggested here for other Haskell projects. -fPIC does even fail as it is not a Windows thing, anyway.
  The error is the same for off- and on-chain functions. So the INLINABLE pragma is not to blame.
  Does this have anything to do with the PlutusTx compiler?
upvoted_answer: This may have to do with Haskell being a functional language. Meaning that unlike imperative languages, there is no 'breakpoints' due to the nature of the language.
  The other link you mentioned only works with I/O operations where they follow an 'imperative' style. The answer for your question would be to find a new way to debug functional programs seeing as they dont work with imperative style debugging.