Revision history for DebuggerRunning


Revision [21672]

Last edited on 2016-11-07 06:39:39 by fxm [Formatting]
Additions:








Revision [21493]

Edited on 2016-05-21 08:41:43 by CountingPine [Try and make more friendly to read]
Additions:
The debugger is in the ##bin\win32## or ##bin\dos## directories (the **GDB**.EXE file), for the Windows and DOS versions respectively. It usually comes already installed in most Linux distros.
(Note: all commands should be typed without quotes and then ##[return]## must be pressed.)
- Compile the source code for your program in debug mode
- use the ##[[CompilerOptG|-g]]## command-line option to add debugging support, e.g. ##fbc -g myapp.bas##.
- Load your compiled program in GDB
- For example, in Windows/DOS: ##gdb myapp.exe##
- Set any arguments you want to send to your application
- For example: ##set args arg1 arg2 argn##.
- You can also run GDB and pass the arguments directly to the application been debugged: ##gdb --args myapp.exe arg1 arg2 arg3##.
- Ensure GDB can see your program's source code directory
- If the executable isn't in the same directory of the source files where it was compiled, type: ##dir path/to/my/application/sources##.
- Set a breakpoint in your program
- Place a breakpoint in the first line using: ##b main##.
- To place a breakpoint in a function called ##func## use: ##b FUNC##.
- Note: fbc exports variable/function names to UPPERCASE. GDB is case sensitive by default, but you can use the ##set language pascal## command to change GDB to case-insensitive mode.
- Use GDB shortcuts to run your code or to step through it
- Type ##r## to start running the application.
- Type ##n## to step to the next line, stepping over function calls.
- Keep pressing ##[return]## to step forward to the next line.
- Type ##s## to step into function calls.
- As above, keep pressing ##[return]## to step through.
- Type ##c## to continue execution until the next breakpoint.
- Use GDB shortcuts to inspect variables
- Use ##print VAR_NAME## to show the contents of the variable called ##var_name##.
- GDB supports pointer/pointer field dereferencing, indexing and arithmetics too, so ##print *MYPOINTER## will also work.
- (note: undeclared variables or the ones with suffixes like ##%## ##&## ##!## ##""#""## ##$## can't be printed).
- Use ##disp VAR_NAME## to display the contents of a variable called ##var_name##.
- Use ##watch VAR_NAME## to stop each time a variable called ##var_name## is changed.
- Additional commands:
- Use ##r## again to restart the application when it finishes.
- Type ##q## to quit.
- Type ##help## to see a list of commands, there are many others.
Deletions:
The debugger is in the bin\win32 or bin\dos directories (the **GDB**.EXE file), for the Windows and DOS versions respectively. It usually comes already installed in most Linux distros.

(Note: all commands should be typed without quotes and then [return] must be pressed.)

- Compile the sources using the -g cmd-line option to add debugging support.
- Load it in GDB using: ##"gdb myapplicationname.exe"##
- Set the arguments to the application been debugged using: "set args arg1 arg2 argn". You can also run GDB and pass the arguments directly to the application been debugged: "gdb --args myapp.exe arg1 arg2 arg3".
- If the executable isn't in the same directory of the source files where it was compiled, type: ##"dir path/to/my/application/sources"##.
- Place a breakpoint in the first line using: "b main". To place a breakpoint in a function called "abc" use: "b ABC" (note: all in uppercase, GDB is case sensitive by default, but you can use the "set language pascal" command to change GDB to case-insensitive mode).
- Type "r" to start the application.
- Type "n" to step over function calls. Keep pressing [return] to skip to the next line.
- Type "s" to step into function calls. Same as above.
- Type "c" to continue execution until the next breakpoint.
- Use "print ABC" to show the contents of the variable called "abc". GDB supports pointer/pointer field dereferencing, indexing and arithmetics too, so "print *MYPOINTER" will also work. (note: undeclared variables or the ones with suffixes like % & ! # $ can't be printed).
- Use "disp ABC" to display the contents of a variable called "abc".
- Use "watch ABC" to stop each time a variable called "abc" is changed.
- Use "r" again to restart the application when finished.
- Type "q" to quit.
- Type "help" to see a list of commands, there are many others.


Revision [20779]

Edited on 2016-03-12 11:54:43 by fxm [Formatting]
Additions:



Revision [14662]

Edited on 2010-06-19 04:22:20 by DkLwikki [Reverted previous change.]
Additions:
{{fbdoc item="back" value="DocToc|Table of Contents"}}
Deletions:
{{fbdoc item="back" value="FBWiki|Main Page"}}


Revision [14637]

Edited on 2010-06-15 11:32:24 by DkLwikki ["Back to Main" instead of "Back to TOC"]
Additions:
{{fbdoc item="back" value="FBWiki|Main Page"}}
Deletions:
{{fbdoc item="back" value="DocToc|Table of Contents"}}


Revision [12059]

The oldest known version of this page was created on 2008-01-03 18:32:04 by ElSairon ["Back to Main" instead of "Back to TOC"]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki



sf.net phatcode