{"id":647,"date":"2022-01-31T13:05:09","date_gmt":"2022-01-31T16:05:09","guid":{"rendered":"https:\/\/gladiston.net.br\/?page_id=647"},"modified":"2023-03-09T11:09:02","modified_gmt":"2023-03-09T14:09:02","slug":"de-ola-ao-fpdebug","status":"publish","type":"page","link":"https:\/\/gladiston.net.br\/en\/programacao\/lazarus-ide\/de-ola-ao-fpdebug\/","title":{"rendered":"Say hello to FpDebug"},"content":{"rendered":"

Prior to version 2.2, Lazarus IDE (only Lazarus from now on) used a GNU tool called GDB. As of version 2.2 Lazarus now has an internal debugger that according to many opinions is better and faster, it's called FpDebug.<\/p>\n\n\n\n

First of all, switching to FpDebug is not mandatory, GDB is still possible and on some occasions you will still see a warning message for the lack of GDB installed like this one:<\/p>\n\n\n\n

\"\"
The IDE still misses the GDB on the system, but can ignore it.<\/figcaption><\/figure>\n\n\n\n

After the IDE is installed, go to Tools|Options|Debugger|General and you will see this:<\/p>\n\n\n\n

\"\"
'Additional search path' should have the path to gdb.exe but is no longer needed<\/figcaption><\/figure>\n\n\n\n

Traditionally the location now called 'Additional search path' should have the path to gdb.exe, but as I said, it's not gdb.exe anymore so for now we can leave it blank. Here are some options that I think are useful to have checked:<\/p>\n\n\n\n

Show message on stop with Error(Exit-code<>0)<\/strong>: The posix standard for any program whether it is windows or linux environment is to end with 'exit code' equal to zero to indicate to the operating system and\/or subsequent programs that the program has finished without errors, any other code will indicate an alert(warning) or fatal error(fatal error). Windows usually returns values less than zero or greater than 255 to refer to alerts and greater than 1\u2026254 to indicate errors, but in my experience as a programmer analyzing other programs I come to the conclusion that in this environment there is no standard except for commands (TUI) commands that usually repeat the MSDOS 'exit code', for example 'exit code' equals '2' to indicate 'file not found'. Pascaleiros, Javeiros, PHPeiros,\u2026 and a legion of programmers develop their own logging and debugging pattern, but it would be great if error messages went to stderr\/stdout and that every program had an 'exit code' documented and following some pattern , so it would be much easier to program and debug <\/em>program crashes using the operating system itself without needing assistance from other programs or 'inhouse' solutions made by the programmers themselves. That's why I keep this option turned on.<\/p>\n\n\n\n

Automatically close the assembler windows, after source not found<\/strong>: When we are debugging <\/em>line by line (step by step) the source code is triggered and even jumps to other codes that may not be available and in this case a window of debugger <\/em>which shows the current code in assembly. Unfortunately my knowledge of assembler language has been lost over time so although useful, I have nothing to do when debugging it. That's why I keep this option turned on.<\/p>\n\n\n\n

Now go to Tools|Options|Debugger|Debugger backend and you will see this:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Se n\u00e3o estiver vendo o fpDebug, \u00e9 provavel que o gdb ainda seja o padr\u00e3o da sua IDE, se desejar trocar(e vai querer) siga as orienta\u00e7\u00f5es:<\/p>\n\n\n\n