ok several issues...
All of them assume 64bit IDE / 64bit target.
moreover very often CPU windows pop-up
It's a known issue together with "F8 sometime steps in, instead of over". Some problem either in fpc or gdb.
If this happens, then 2 things can be done, both in Tools > Option > Debugger
1) Debugger > General: "Automatically close the asm win". Once you step back to source code...
2) Debugger > General (Laz 2.1: Backend): property grid: FixIncorrectStepOver = True
with "F7" the debug jump to next line ignoring the breakpoint
Actually do you mean "ignoring the "step in"?
because you are already stopped at the breakpoint. You want to step into the function (but in the function "result := true" there is no breakpoint)?
IIRC 2.0.10 came with GDB 8.2 => 2.0.12 switched back to GDB 7.3.50
The reason is that 8.2 only works correct for people with a latin based locale. Any one else gets there entire environment variables scrambled.
Until a few days ago, 7.3.5 was the only build available that would work on other locales.
I did spent some time (about 2 weeks) earlier this year, to get a newer GDB. I uploaded this (8.3.1, and yes that is old...) now,
despite not having tested it yet. (Still not got the time to test it).
And yes it takes a lot of time to build gdb (or maybe I have not yet found the instructions how to do that faster).
Usually errors happen about half an hour into the compile. Then you have to do trial and error, how to fix it, and each trial is another half an hour.
- I had to extensively search the sources to find, that it will only work with cygwin.
- I had to then to lots of trial and error on gbd 10 under cygwin, until I got an error that I could trace via google to a report that all gdb over version 9 are broken for cygwin.
- And then it was trial and error to find the settings to compile gdb 8.3.1 (ok, I could have saved some time, and build it none static, and include about 5 or 6 more dll / the cygwin dll itself can not be avoided, unless maybe one uses a real old version of cygwin)
- end of rant on building gdb.
So your choice for Lazarus 2.0.12 is to download a different gdb from
https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2064%20bits/Alternative%20GDB/If 8.2 works for you, go for it.
Or try 8.3.1.
Lazarus 2.2 will have 7.3.5. Unless I find the time to test 8.3.1 (feedback on it will help)
Alternatively, use FpDebug => package LazDebuggerFp / search the wiki