Difference between revisions of "Debugger"
From Lazarus wiki
Jump to navigationJump to searchm |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 11: | Line 11: | ||
* [[IDE Window: Assembler| Assembler]] | * [[IDE Window: Assembler| Assembler]] | ||
* [[IDE Window: Breakpoints| Breakpoints]] | * [[IDE Window: Breakpoints| Breakpoints]] | ||
| − | |||
* [[IDE Window: Call Stack| Call Stack]] | * [[IDE Window: Call Stack| Call Stack]] | ||
* [[IDE Window: Debug History| Debug History]] | * [[IDE Window: Debug History| Debug History]] | ||
| Line 34: | Line 33: | ||
* [[lldb]] - macOS debugger | * [[lldb]] - macOS debugger | ||
* [[Debugging with Valgrind]] | * [[Debugging with Valgrind]] | ||
| + | * [[Debugger Setup]] | ||
=== GDB === | === GDB === | ||
Latest revision as of 15:57, 9 April 2022
│
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.
- Assembler
- Breakpoints
- Call Stack
- Debug History
- Debug Output
- Debugger Options
- Class Options Frame
- General Options Frame
- Evaluate/Modify
- Event Log
- Local Variables
- Registers
- Run parameters
- Terminal Output
- Threads
- Variable Inspector
- Watch list
- Watch Properties
See also
- Debugger Status
- FpDebug
- lldb - macOS debugger
- Debugging with Valgrind
- Debugger Setup
GDB
- GDB - GNU debugger
- Creating a Backtrace with GDB
- Debugging - GDB tricks
