How to use the Event Log?

[WooBean]

Lazarus IDE configuration contains an option Event Log as a part of IDE Options/Debugger.
I can not find any clue what is it for and how to use it.
Any pointer?

See attached file from Lazarus 2.2.4 (Win 64).

[Martin_fr]

Menu: View > Debug Windows > Event Log

https://wiki.lazarus.freepascal.org/IDE_Window:_Event_Log (wiki is outdated)

[WooBean]

Menu: View > Debug Windows > Event Log

https://wiki.lazarus.freepascal.org/IDE_Window:_Event_Log (wiki is outdated)

Thanks for a clue.
I tried to follow it by changing debugger from default FpDebug (what do not promise a lucky way) to GDB (just to follow a wiki guidance) but ... ups.
I have got the below:

 

[Martin_fr]

I tried to follow it by changing debugger from default FpDebug (what do not promise a lucky way) to GDB (just to follow a wiki guidance) but ... ups.

Which page on the wiki? That page is outdated.

The current recommendation for debugger:

On Windows and Linux: FpDebug
On Mac: LLDB with FpDebug

Use GDB (or gdb server), only if you
- Do Remote debugging (to another machine / using gdbserver)
- Do not have an Intel/AMD (compatible) cpu. (Except on Mac, where M2 is supported by the above recommendation)
  (And except for cross AVR, for which there is an FpDebug variant)
- Have a 32bit IDE but want to cross debug a 64bit application (better get the 64bit IDE)
- On Mac, and have this issue: https://forum.lazarus.freepascal.org/index.php/topic,61261.0.html
- Very few other edge cases.


As for the error: That is (99% likely) a bug in GDB. Nothing we can do (hence we wrote FpDebug, because at least with that: We can do).

In case you want to experiment further with GDB: Make sure you did not use "Dwarf 3" => This increases the chances of crashing GDB.
"Dwarf 2 with sets" is better.
Then try different GDB versions, sometimes older are better. (For Windows we have a few for download, on our sourceforge page).

[WooBean]

Martin, thanks for trying to help.
Which page on the wiki? -Just to explain a wiki jumping, they were as follows -
1: https://wiki.lazarus.freepascal.org/IDE_Window:_Event_Log (last edited 2 February 2021, at 05:30), then as it starts from "Important" link to
2: https://wiki.lazarus.freepascal.org/Debugger_Setup (last edited 13 May 2022, at 10:07) and then  (from "See also") to
3: https://wiki.lazarus.freepascal.org/IDE_Window:_DebuggerGeneralOptionsFrame (edited 11 October 2019, at 19:10) and
4: https://wiki.lazarus.freepascal.org/IDE_Window:_DebuggerClassOptionsFrame (edited 5 February 2021, at 18:21) which points back to [2:].

TODO for me - a lot of jumping inside IDE and documentation (including  the wiki) ahead.

PS. I'm trying to deeply and effectively debug  Lazarus (2.2.4) project compiled with default options for Debugging IDE:
-gw3  //Generate DWARFv3 debug information
-gl   //Use line info unit (show more info with backtraces)
-gh   //Use heaptrace unit (for memory leak/corruption debugging)
-gt   //Trash local variables (to detect uninitialized uses; multiple 't' changes
-Co   //Check overflow of integer operations
-Cr   //Range checking
-Ci   //IO-checking
-Sa   //Turn on assertions

[petebanx90]

The "Event Log" option in Lazarus IDE's configuration, found under IDE Options/Debugger, is typically used to view and track events, messages, or notifications related to the debugging process and program execution. It can be a helpful tool for developers to understand what's happening behind the scenes while debugging their code.

You can use the Event Log for various purposes, including:

Error and Warning Messages: It can display error messages, warnings, or notices generated during debugging, which can help you identify issues in your code.

Execution Flow: It may show the sequence of events, such as function calls, variable changes, or breakpoints being hit, providing insights into the program's execution flow.

Debugging Information: The Event Log can provide information about breakpoints, watches, and other debugging actions you've set up.

Exception Handling: If an exception is thrown during debugging, the Event Log can capture details about the exception, making it easier to diagnose and fix the problem.

To use it effectively, you can look for specific messages or events that appear in the Event Log when you're debugging your application. It can be a valuable tool for diagnosing issues and understanding the runtime behavior of your code.