Click above to get retro games delivered to your door ever month!

 6.1 Using the FiveWin debugger
--------------------------------------------------------------------------------

   FiveWin offers its own Windows debugger version. In order to use the
   debugger just compile using /b.

                 clipper MyApp /n/b

   If you use FiveWin SAMPLES\Build.bat, you can specify a second
   parameter after the name of your app:

                 build MyApp /b

   When you execute your application the FiveWin debugger will automatically
   appear. FiveWin debugger requires the DLL we provide called FWDBG.DLL.

   Building a Windows debugger is really a very complicated task since
   there is no a way to 'STOP' Windows activity: Windows is constantly
   interacting with the user, so if we just move the mouse a lot of
   activity starts occurring. Even Borland has been using text mode
   debuggers for its Windows products (Borland C++), that gives you a
   good idea how difficult it is.

   Also, using a debugger in a event-driven and OOPS architecture is something
   very difficult.  Anyhow we have provided it as a help to find some
   bugs you may be looking for.

   Honestly we almost never use the debugger. Instead we use some MsgInfo()
   function calls showing certain values at certain application execution
   points.  We find this much more easy to manage and it gives very
   good results.

   Also FiveWin generates a very complete Error.log file when an error
   occurs. Use the info we provide there to help you find the bugs.

   You may use the FiveWin debugger only in those circumstances where
   no other solution is found. Anyhow, we strongly recommend that you
   contact us if there is a problem you can't solve by yourself (instead
   of spending a lot of time searching and searching!)