- create a directory and copy inside fbdebugger.exe and fbdebugger_help.chm
- If you prefer compile you own version :
Fbc -s gui fbdebugger.bas fbdebugger.rc. Don't forget to put the buttons folder and the icon file with these two files.

ALWAYS save your job before debugging

- start fbdebugger *
- click on file button and select a exe **
- debugging is starting.
- use step button or an other execution buttons

* if FBDebugger is already running a message box is displayed offering the choice to stop or to continue with one more instance.
** In all cases the compilation must be done with the g parameter to add the debug data inside the exe. These data are procedures and variables names and pointers for each executable line.

Nota some lines, such dim shared foo as integer, are not executable because the compiler need not to generate assembly code.
To see no executable lines

- Fbdebugger accepts filename in commandline so you can start it in a .bat or from an other program.

     Example with Fbedit :
     - Select debug/quick run option in the options menu and enter (or use the file explorer button) the path/name of fbdebugger.
     - Then in the make menu select run with debug launch fbdebugger with the debuggee.

     - An other way : select the tools menu option in the options menu and create an entry Fbdebugger.
     - Then in the tools menu a new option offers to launch fbdebugger without parameters.

- You can drag and drop an exe directly on FBdebugger inside the file explorer.
- You can also drag and drop an exe anywhere on the main window of FBdebugger the exe is immediatly debugged.

- You can do the same with a .bas. It is firstly compiled then debugged. In this case some informations about FBC.exe must be filled [settings]