DesignTime-Package debuggen?

[Kas Ob.]

I want to share my experience with older versions like XE8 with something similar that might be relevant or not, just food for thought.

Zitat:

set start parameters
* host = $( BDS )\bin\ bds .exe
* param = -pDelphi
* path = $( BDS )\bin

In my XE8 i don't have what named "path" !!, i have "Working Directory" and "Source Path", so i will assume they renamed "Source Path", in all cases..

If you build and saved new and simple a project les say project1.exe, then it will work fine and debug fine and you can put break points and more importantly you can see symbols being resolved like method names...
Now if you run this project1.exe by Windows Explorer then click choose to attach to process then we have two output:
1) if the project1.dpr is opened in the IDE then symbols will be resolved.
2) If no projects are opened or another project is opened, then the Debugger ignore all TDS info and no symbols will be resolved or shown, the debugger can't recognize the project1.exe and handle it as unknown without any debug info..

This is strange and frustrating, and it is a failure... the debugger had it all in TDSinfo yet it don't try.

Anyways, i just wanted to give you hint about this behavior which very likely to be the case with lost debug info and symbols recognition.

To confirm if this is the case, i suggest to repeat your steps, then use VMMap from https://learn.microsoft.com/en-us/sy...ownloads/vmmap , find your package in memory of the debugged bds process,(yup thee is no search, so sort by details) it will be colored as purple and marked as image, expanding that will see .text and .itext sections and their addresses, use these addresses with in your debugger and browse these memory regions to see if your debugger (the one that debugging) is resolving your package symbols and if it did resolve any to that extent..

Now, back to the paths, i don't know if this will help or not but it might be failing/confusing the opened dpr project with running BDS file instead of loaded package/library, so try to attach the bds.exe instead of loading it, who knows... it might resolve the loaded package project and resolve it, hence allowing you to debug, while losing the starting point, but this can be tweaked or workaround with different hacks, might be later talk for different situation.