This is based on Lazarus 2.0
- GNU Debugger (gdb)
- The first debugger that was supplied with Lazarus. This debugger uses GDB as backend. The IDE performs translations between gdb's none Pascal-ish interface and the interface provided by the IDE. Package: LazDebuggerGdbmi
- GNU Debugger through SSH (gdb)
- Allows to launch GDB over an ssh connection for remote debugging. This has however some serious limitations. Package: LazDebuggerGdbmi
- GNU remote debugger (gdbserver)
- Remote debugger using GdbServer (part of the gdb suite). Package: LazDebuggerGdbmi
- LLDB Debugger (Alpha)
- A basic LLDB based backend. This is a prove of concept implementation. The IDE displays raw LLDB output (no translation, no clean-up...) and there are no plans to add translation of the LLDB output. For using LLDB on Pascal applications the "LLDB Debugger (with fpdebug)" should be used. Package: LazDebuggerLldb
- LLDB Debugger (with fpdebug)
- This debugger uses LLDB as a backend. In order to display Pascal-style results, it uses the "fpdebug" engine to show locals/watches. LLDB is used to control stepping, breakpoint and execution. For reading data LLDB is used to read the raw memory only. Package: LazDebuggerFPLldb
- GNU Debugger (with fpdebug)
- Using GDB for stepping/breakpoints/... and FpDebug for watches. Package: LazDebuggerFPGdbmi
- FpDebug / LazDebuggerFp - integrated DWARF debugger / (Known issues)
- A new debugger completely implemented in Pascal. This debugger implements the DWARF standard (currently 2 and 3 are partly implemented). It has special implementations added to interpret info provided by FPC. It can currently be used on Windows and Linux (very basic support for MacOS). Package: LazDebuggerFP
- FpDebug / LazDebuggerFpRspRemote
- A new remote debugger to communicate with a gdbserver stub using gdb's remote serial protocol over tcp/ip (in future this could be expanded to include serial/UART). This debugger inherits from LazDebuggerFP, hence in principle supports the same functionality. Currently it only supports the AVR target. Not stable yet. Package: LazDebuggerFpRspRemote
- DAB / LazDABDebugger
- The Debug Adapter Protocol (DAB) is a protocol to abstract the communication between a Debugger-frontend like Lazarus, and an underlying debugger like FpdServer. LazDABDebugger is a debugger that connects to (any?) DAB-adapter. This makes is possible to debug other languages or different platforms within Lazarus.
- DAB - FpdServer / LazFPDServerDebugger
- A derivative of LazDABDebugger specifically shaped to work with FpdServer, a debugger based on FpDebug that supports the DAB-protocol.
- For the GDB and LLDB based debugger, support is indicated based on the assumptino that your version of GDB supports this. Support indication is generally based on current GDB/LLDB for mainstream OS.
- Fp-Debugger currently only works for Windows and Linux
- The "LLDB Debugger (Alpha)" is not included below. It is a by-product of the "LLDB+FpDebug". It is not actively developed/maintained, other than what is needed for "LLDB+FpDebug".
|Linux||Y||Y||Y||Y||Depends on availability
of a stable LLDB
|Mac||Depends on availability
of a stable
and codesigned GDB
|Windows||Y||Y||Y||Y||Depends on availability
of a stable LLDB
|Run to first line (Step)||/||Y||Y||Y||Y||?||N||For GUI apps the first line is in the code generated by the IDE|
|Run to line at cursor||Y||Y||Y||Y||N||Y||Lazarus 2.2 and higher|
|Attach||Y||Y||Y||Y||?||Lazarus 2.2 and higher|
|Detach||Y||Y||Y||Y||?||Lazarus 2.2 and higher|
Restart the external debugger (gdb/lldb)
|Debugger stopped dialog when app exits||Y||Y||Y||Y||Y||Y||Configurable|
|Run without debugging||+ +||Y||Not debugger specific|
|Step over line||Y||Y||Y||Y||Y||Y|
|Step into line||Y||Y||Y||Y||Y||Y|
|Step (over) to line at cursor||Y||Y||Y||Y||N||Y||"STEP OVER" - This works only within the current procedure.
It will go to the selected line, or stop if the current procedure is left.
|Run to line at cursor||Y||Y||Y||Y||N||Y||Only Lazarus 2.2 and higher|
|Step out (of current function)||+||Y||Y||Y||Y||Y||Y|
|Step over asm||+||Y||Y||Y||Y||Y||Y|
|Step into asm||+||Y||Y||Y||Y||Y||Y|
|Smart source or asm stepping (over/into)||Y||Y||Y||Y||Y||Y||Assign one key (one for "over", one for "into") that acts as source-line or asm stepping, depending on window focus|
|Pause||Y||depends on gdb, mostly "No"||Y||Y||Y||Y|
|Step: steps over "none breaking" breakpoint||Y||Y||Y||Y||?||Lazarus 2.0 or 2.2 ?||Any "step" command will continue to its step-end after a "none breaking" Breakpoints. This is a Breakpoint that has its break property turned off. It may record a snapshot, log a message, or enable/disable other breakpoints.
|Step: steps over ignored exceptions||Y||Y||Y||Y||?||Lazarus 2.2||Only for standard fpc exception handling. And (Lazarus 2.2) SEH on Win64. |
Win32 and other OS structured exception handling are not supported (Ignored exceptions will turn Stepping into Running).
|Source-Step: steps from except to finally or except||Y||Y||Y||Y||?||Lazarus 2.2||Only for standard fpc exception handling. And (Lazarus 2.2) SEH on Win64. |
|Executable/Code line indicators||Y||Y||Y||Y||Y||Y||Blue dots in the gutter indicate lines with debug info.|
- Breakpoints / None-breaking breakpoints / Auto-continue breakpoints / Disabled breakpoints
- A breakpoint usually pauses your app, in addition it can perform tasks like logging a message (debugger event log), dumping data to the log, taking a snapshot (debugger history).
A none-breaking breakpoint will perform those extra tasks, but not pause your app.
An auto-continue breakpoint will pause your app (and perform any other action) for a given amount of milliseconds (during which you can use the pause button, to pause permanently), after that it will continue your app. It usually continues using "Run", therefore loosing any current single-step action
A disabled breakpoint will do nothing. It is as if it does not exist.
- Stepping and breakpoints / exceptions
- If any debugger pauses the target-app at a breakpoint or exception while single stepping, then the single-step is lost. The breakpoint/exception may be in a deeply nested called function, and you cannot continue the single-step. I.e. there is no build in way to get back to the function where you started your step, and finish this step. For this you need to go through the callstack yourself and find the start location and use breakpoints
- Stepping and none-breaking-breakpoints / Ignored-exceptions
- Most/All? debugger backends can in this case continue to the position where the single-step would have ended. (This may be limited for asm stepping). In case of an exception the single step will end at the next finally or except. "Next" from the point of view of the step-command. I.e., any finally inside a "stepped over function" will be stepped over, but any finally on the same level as the step began will be used as end point. If there is none on the same level, then the next outer will be used.
This feature relies heavily on FPC implementation details. Thus it may not work with newer FPC versions.
Breakpoints / Exceptions
|Breakpoint on Source Line||Y||Y||Y||Y||Y||Y|
|Breakpoint on Assembler Line||Y||Y||Y||Y||Y||Y|
|Watchpoint / Breakpoint Data||Y||Y||Y||Y||?||Partial||Amount/Size is limited by architecture
Intel based systems usually have 4 Watchpoints, each with a max size of 32 bit (64 bit on 64bit CPU)
|Conditional Break/Watch-point||(Y)||(Y)||(Y)||(Y)||?||Y||GDB based debuggers are limited to GDB's understanding of the conditional expression|
|Enable/Disable Break/Watch-point according to program flow||Y||Y||Y||Y||Y||Y||Enable/Disable a breakpoint (or a group of) when execution passes through a pre-defined point in your code.
So you can setup that the debugger will only break/skip-breaking, when the code is called in a specific order, or from a specific outer subroutine.
|Ignore exception by class||Y||Y||Y||Y||Y||Y||Configurable for each project|
|Break/Watch-point overview Window||+ +||Y||Y||Y||Y||Y||Y|
|TODO: .... Document Breakpoint properties||.||.||.||.||.||.|
|TODO: .... Document Breakpoint actions||.||.||.||.||.||.|
- Some functionality depends on the ability to use "Pause". If "Pause" does not work, break/watch-points can not be changed/added/removed while the target app is running. Only when the target app pauses at a breakpoint (or for other reasons), then can changes be made.
|Threads||+ +||Y||Y||Y||Y||Y||Y||Running State indicator may not be accurate|
|Inspect||+||Y||Y||Y||Y||Y||Y||View members in property Grid. Double-click to inspect members|
|Evaluate / Modify||+||Y||Y||Y||Y||?||Only Evaluate
|Watch/Inspect Class Properties||N||N||N||N||N||N||Using "DWARF" properties that refer directly to a field (no getter method) are shown.|
|Watch/Inspect Function calls||N||N||N||N||N||N|
|Use Instance type/class||Y||Y||Y||Y||Y||Y||By default the debugger shows variables according to their declared type/class.
"Sender: TObject" will only show as TObject.
|Tooltip / Hint||Y||Y||Y||Y||Y||Y|
|Tooltip / Hint => Auto-deref pointer||Y||Y||Y||Y||Y||Y|
|Tooltip / Hint => Use Instance Class||Y||Y||Y||Y||Y||Y|
|Paste value into Watches window||Y||Y||Y||Y||Y||Y||Paste directly into watches window, no need to press "Add new watch"|
|Drag/Drow value from source-editor to Watches window||Y||Y||Y||Y||Y||Y|
|TODO: .... Document Watches properties||.||.||.||.||.||.||
|History||+ +||Y||Y||Y||Y||Y||Y||Allow to review Watches/Locals/Stack from when your app was previously paused.
This does not restore the state of the application. It only allows to view the value that the debugger evaluated previously.
|History - Import / Export||Y||Y||Y||Y||Y||Y||
|Event log||+ +||Y||Y||Y||Y||Y||Y|
|View internal debug output||Y||Y||Y||Y
|?||Not applicable||View communication with the external debugger. For troubleshooting|
|Cross debugging 32<>64bit||Y||Y||Y||Y
Win-64bit IDE can debug 32 bit target
Win-64bit IDE can debug 32 bit target
|Edit source code while debugging||Y||Y||Y||Y||Y||Y||