Difference between revisions of "Debugger"

From Lazarus wiki
Jump to navigationJump to search
m (→‎See also: Added entries)
Line 7: Line 7:
  
 
Debuggers also monitor the contents of program [[Variable|variables]] and often produce a back-trace showing the instructions that were being executed immediately before a program failure occurred.
 
Debuggers also monitor the contents of program [[Variable|variables]] and often produce a back-trace showing the instructions that were being executed immediately before a program failure occurred.
 +
 +
 +
* [[IDE Window: Assembler| Assembler]]
 +
* [[IDE Window: Breakpoints| Breakpoints]]
 +
* [[IDE Window:Breakpoint properties|Breakpoint properties]]
 +
* [[IDE Window: Call Stack| Call Stack]]
 +
* [[IDE Window: Debug History| Debug History]]
 +
* [[IDE Window: Debug Output| Debug Output]]
 +
* [[IDE Window: Debugger Options| Debugger Options]]
 +
* [[IDE Window: DebuggerClassOptionsFrame| DebuggerClassOptionsFrame]]
 +
* [[IDE Window: DebuggerGeneralOptionsFrame| DebuggerGeneralOptionsFrame]]
 +
* [[IDE Window: Evaluate/Modify| Evaluate/Modify]]
 +
* [[IDE Window: Event Log| Event Log]]
 +
* [[IDE Window: Local Variables| Local Variables]]
 +
* [[IDE Window: Registers| Registers]]
 +
* [[IDE Window: Run parameters| Run parameters]]
 +
* [[IDE Window: Terminal Output| Terminal Output]]
 +
* [[IDE Window: Threads| Threads]]
 +
* [[IDE Window: Variable Inspector| Variable Inspector]]
 +
* [[IDE Window: Watch list| Watch list]]
 +
* [[IDE Window: Watch Properties| Watch Properties]]
  
 
== See also ==
 
== See also ==
 
 
* [[Debugger Status]]
 
* [[Debugger Status]]
 
* [[FpDebug]]
 
* [[FpDebug]]
Line 16: Line 36:
  
 
=== GDB ===
 
=== GDB ===
 
 
* [[GDB]] - GNU debugger
 
* [[GDB]] - GNU debugger
 
* [[Creating a Backtrace with GDB]]
 
* [[Creating a Backtrace with GDB]]
 
* [[Debugging - GDB tricks]]
 
* [[Debugging - GDB tricks]]

Revision as of 13:37, 27 July 2020

English (en) suomi (fi) français (fr)

A debugger is a program used to test and debug other programs. Often, when using the debugger, the program being scanned is compiled with special compiler settings which adds information for tracing errors. This way, the debugger knows what the source code file is named for and the line from which the code is executed. But when the program works well, you can remove this data and reduce the size of the binary.

Debuggers also monitor the contents of program variables and often produce a back-trace showing the instructions that were being executed immediately before a program failure occurred.


See also

GDB