I'm using RAD Studio 10.2.3 Tokyo.
Research
Related to this question, and this issue I run into trouble when debugging my flagship application that extensively utilizes runtime BPLs as a plugin system.
The problem occurs only when compiled and debugged as a Win64 application, and using Delphi's Win64 internal debugger. Delphi's Win32 internal debugger does not have this problem.
When using "load all symbols" in the debugger options, I miss stack and local symbols info for some units but not other units in the same BPL (check screenshots).
However, when I use the option to load debug info for specific BPLs, and only in my runtime BPL all units have local symbols info. Logically, I am missing debug info for all other units.
Of course, I dont like having to specify each symbol table specifically, I would rather load all symbol tables and not have to mess with it.
I have also experimented with using the symbol tables path, but this made no difference in loading the debugging results.
Question
Has anyone else experienced this, and found a better workaround than specifying which symbol tables to load?
Maybe something like an INI file, or Registry setting, or other solution for the Win64 debugger?
Some background info and screenshots below
Debugging view when turning on "Load all symbols"
Debugging view when using specific symbol table for this runtime BPL
Settings for specific symbol table loading
来源:https://stackoverflow.com/questions/51098092/is-there-a-limit-to-the-delphi-win64-debugger-loading-symbols