To inspect property values you may find it easier to add LazLogger to your uses clause and insert DebugLn() calls at the critical points (or just use WriteLn() calls, though on Windows this requires {$APPTYPE CONSOLE}).
Perhaps you are used to the superior Delphi debugger. But remember that has been honed over 30 years by professionals paid to work on it every day, and is Windows-specific (the Delphi IDE is Windows-only) and largely written in assembler/C, not Pascal.
Lazarus has been cross-platform from the outset, and its reliance on a third-party debugger (gdb) is an acknowledged weakness. gdb was never designed to debug Pascal, and frankly it is a near miracle that Lazarus developers have manged to get it to work as well as it does outside its preferred C environment. gdb has no concept at all of Pascal properties. Several attempts at a native debugger for FPC/Lazarus are under way, but none has yet reached production quality, and so reliance on gdb persists. I wish I had the skills to help in this endeavour, because for some it is a shortcoming in Lazarus that puts them off entirely.
If you've ever browsed the LCL sources you'll see that the developers themselves use DebugLn() calls regularly, and often leave them in the sources commented out.