Afaik included is 7.3Thanks for answer.
Alternative at https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2064%20bits/Alternative%20GDB/
The 2nd question is what debug info your project uses (and what version of fpc).Lazarus 1.8.4, so FPC 3.0.4
Debug info applies separate to project and packages. (Stabs may cause problems / if it is supported by your version of fpc / try dwarf, but not dwarf 3 / try additions and overrides to apply it to all code).
You can also try -Xe external linker to see if it make a differenceWith this (in Project Opttions/Custom Options) not compiled - project1.lpr(15,1) Error: Error while linking.
"shamanism" :D I agree.Сontrariwise. With -O- or -O1 the debugger does not work.
Anyway, although -O2 should be very friendly to GDB can you still debug in = -01? It is not my (main) platform, but I can try tomorrow.
Lazarus 1.8.4, so FPC 3.0.4
I try all type of debug info (early "Any changes to the "Debugging" tab in the project option").
What is arguments for -stack-list ?https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Stack-Manipulation.html
"shamanism" :D I agree.
Anyway, although -O2 should be very friendly to GDB can you still debug in = -01? It is not my (main) platform, but I can try tomorrow.
This still leaves packages compiled with other debug info.A very simple project without any packages. I attached it to the message.
Using "Additions and Overrides" you can set options for all packages. (Or change it for the package in which the breakpoint is, including 2 level of callers)
I uploaded 8.1 for 64 bit https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2064%20bits/Alternative%20GDB/Yes, you're right, no change.
But I doubt it will make a difference.
You may try and go to the debugger options and in the field "debugger_startup_options" enter:No changes
--eval-command="set max-value-size 50000"
What is the output (last couple of lines) in Menu: View > Debugger > Debug Output?I finally the compared logs in normal case and erroneous. This is similar to GDB failing when trying to get a value from a complex structure variable if its value is not yet defined (out parameter).
I can reproduce it with different gdb versions (haven't tried 32 bit yet).Can you give us what gdb version? <smile> Keeps people from their normal work....
Anyway debugging gdb itself is not currently something I have time to put on my list...
Btw, If you go for Lazarus trunk, you may want to try LazDebuggerFp
Can you give us what gdb version? <smile> Keeps people from their normal work....