I added a testcase for "lldb with fpdebug".
Currently it only focuses on watch evaluations. Stepping, breakpoints and the like are not yet tested.
If you are
- on trunk, at/past revision 60012
- on fixes2.0, at/past revision 60013
then you can run it. (and it be nice if you do, please)
The test is in components\lazdebuggers\lazdebuggerfplldb\test
TestFpLldb.lpi
Before you can run it you need
* CONFIG
copy and edit
fpclist.txt.sample => fpclist.txt
lldblist.txt.sample => lldblist.txt
Uncomment what you need. Edit the path to your fpc/lldb.
-You can ignore the version info.
-You can add/use one off (or leave away, which means both)
bits=32
bits=64
bits=32,64
-For symbols=gw,gwset,gw3,gw4 you can use any flag that fpc recognizes for dwarf
-You can duplicate a section and extend it with (to pass extra param to fpc)
opts=-O- -godwarfcpp
godwarfcpp is not fully supported
* DIRECTORIES
you may have to rename the folder testapps to lowercase
After you run tests, you should periodically delete any files in it, except for the "lib" folder, which must exist (as an empty folder)
You may create a "logs" folder.
If a file dialog opens, when you run the test, then it did not find the testapps/lib folder.
----------------------
Currently there is a known issue, with global variables from other units (other than the current paused line).
This leads to 61 fails in the "Scope" test. The test will list the number of fails at the end.
----------------------
Running the test may take some time. Between 10 and 30 minutes, depending on your system. Run it from a console, to see it is not stack (it prints dots to the console, from time to time)